NownessAI

com.nownessaiPublished by nownessai.comOfficial publisherv2.3.0Updated Nov 7, 2026

The AI research library for coding agents: current papers, models and tools, explained.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Remote MCP endpoint that gives coding agents access to an AI research library of current papers, models and tools, explained.

What you can do
  • The registry lists no tools, so capabilities are known only from its one-line description.
  • It presents itself as an AI research library aimed at coding agents.
  • It is meant to surface current papers, models and tools with explanations.
  • No further detail on retrieval, search or output format is provided.
When to use it
Consider it when you want a coding assistant to look up recent AI research, models or tooling while working, rather than relying only on its training data. Because no tools or documentation are published, verify what it actually returns before depending on it.
Requirements
A remote MCP endpoint at mcp.nownessai.com over streamable HTTP; OAuth authentication is required. No environment variables, headers or local packages are declared.
Before you install
OAuth grants the server access tied to your account, so review the scopes requested during sign-in. No tool list or documentation is published, so what data it reads or sends to third parties cannot be verified from the listing.

Installation

In SourceWeft

  1. Open NownessAI in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.nownessai%2Fnowness/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nownessai": {
      "type": "http",
      "url": "https://mcp.nownessai.com/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.3.0LatestNov 7, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.