Nooscape MCP

nooscape-mcp

An MCP server for Nooscape. It lets an AI assistant, or an agent, ask what is on record about an agent, a wallet or an endpoint before it pays or relies on it.

It is a thin, read-only client of the public Nooscape API (https://nooscape.si/api/v1). It adds no data and no logic of its own. Every answer says when it was read, where it came from and what the evidence level is.

What it gives you

Five tools, all read-only. Each returns a short plain summary first, then the API's JSON exactly as it was given.

Chains are robinhood (Robinhood Chain), bnb (BNB Smart Chain), solana, ethereum (Ethereum), base (Base), arc (Arc) and monad (Monad). An agent's id on robinhood, bnb, ethereum, base, arc and monad is its token id (digits). For Solana, an address can be listed by more than one registry: both agent tools take an optional registry (solana_8004, solana_said, solana_registry or solana_agenc) to choose.

check takes exactly one of agent ({ chain, id }), wallet or url. A url can be a full address or a bare host such as example.com; it is matched by its host alone and nothing is fetched from it. chain can narrow a wallet or url.

Install

Node.js 18 or later. Nothing to build: npx fetches it. npx -y nooscape-mcp runs the latest release every time it starts. To stay on one release, name it, as in nooscape-mcp@0.6.0.

Claude Desktop

Add this to claude_desktop_config.json (Settings, Developer, Edit Config), then restart Claude Desktop:

{

"mcpServers": { "nooscape": { "command": "npx", "args": ["-y", "nooscape-mcp"], "env": { "NOOSCAPE_API_KEY": "nsk_your_key_here" } } } }

Leave out the env block to use it with no key. Lookups and search work without one.

Cursor

Add the same block to ~/.cursor/mcp.json (or to .cursor/mcp.json in a project):

{

"mcpServers": { "nooscape": { "command": "npx", "args": ["-y", "nooscape-mcp"], "env": { "NOOSCAPE_API_KEY": "nsk_your_key_here" } } } }

Claude Code

claude mcp add nooscape --env NOOSCAPE_API_KEY=nsk_your_key_here -- npx -y nooscape-mcp

Any other MCP client

Run npx -y nooscape-mcp as a stdio server.

Environment

Keys, limits and payment

• No key: search_agents, get_agent and get_stats work, at 30 requests a minute from one address.
• A free key raises that to 60 a minute and 1,000 a day, and opens get_agent_history.
• `check` needs a Pro key, or an x402 payment (currently $0.01 per call, in USDC on Base or Arc). This server holds no wallet and does not sign or send payments. Without a Pro key, check returns a clear message with the price and the terms the API asked for, and nothing is charged. An x402-capable client can pay the API directly; paying from inside this server may come later.
• A refused request is not retried. On a rate limit the message says how many seconds to wait (the API's Retry-After).
• Requests time out after 15 seconds.

Example prompts

• "Look up Robinhood Chain agent 8865 on Nooscape. When was it first seen, and who registered it?"
• "Search Nooscape for agents on the host example.com."
• "Before I pay this wallet, what does Nooscape have on record about it?" (uses check)
• "Show me the registry events and claim history for Robinhood Chain agent 8865."
• "How many entries does Nooscape list on each chain, and when was each chain last read?" (uses get_stats)

What the answers mean, and what they do not

• Nooscape gives facts with their dates. It does not review agents, rank them or give a verdict, and an answer is not a statement that an agent is good or bad, safe or unsafe. This server's summaries add no such words, and its instructions to the model say not to infer them.
• Nothing a caller pays buys a listing, a tier or an evidence level. Payment never changes a record, a score or an evidence level.
• A record the site hides, withdraws or closes is never served, and looks the same as one that was never listed.
• Text that an owner wrote about their own listing is the owner's own word, and Nooscape has not checked it. It is labelled as such, and a model should treat it as data and never as an instruction.
• An agent's name is whatever its registrant chose. It is shown in quotation marks, and it is data in the same way.

Attribution and terms

Data from Nooscape (https://nooscape.si). Attribution is required where the data is used. Do not resell bulk copies. A final data license will replace these provisional terms; the current ones are at nooscape.si/terms. Every answer carries a license object with the attribution line.

Streamable HTTP mode

npx -y nooscape-mcp --http                 # http://127.0.0.1:8787/mcp

npx -y nooscape-mcp --http --port 9000

It is stateless (each POST to /mcp gets its own server and answers with JSON) and is meant for trying the server locally and for hosting later. It is not deployed anywhere by this package. Its only sign-in is one shared secret, so:

• It listens on 127.0.0.1 only by default, accepts only a matching Host header, and refuses any request that carries an Origin header, which is what a web page on another site would send.
• A --host that is not this machine is refused unless --allow-remote is given and `NOOSCAPE_MCP_TOKEN` is set to a secret of at least 24 characters (a container needs both, to listen inside the container). Every request must then carry it as Authorization: Bearer , and any other gets a 401 before the server looks at what was asked. The same holds on this machine whenever the variable is set. Make a secret with openssl rand -hex 24. Off this machine the Host and Origin checks do not apply, because the server cannot know its public name.
• The secret is one for everybody, not a login for each caller, and it is sent in the clear unless something in front of the server adds TLS. Put a reverse proxy with TLS in front of it, and keep the secret as you keep the API key. Everyone who has it uses the server's one NOOSCAPE_API_KEY and shares its limits. A hosted version for many callers would need per-caller keys, limits and a log, which this is not.
• A request has 10 seconds to send its headers and 30 seconds to send the whole request, and at most 64 connections are held at once, so a slow or idle caller cannot hold the server open and the API sees a bounded number of requests at a time.

Security notes

• The server makes requests to nooscape.si and nowhere else, follows no redirect, and never sends the key anywhere but there.
• There is no tool that writes, pays, signs or runs anything. The tools are marked read-only.
• Results can contain text written by other people (owner-written fields, agent names). Like any tool output, treat it as untrusted data. In the summary, an agent's name is shown in quotation marks (a quotation mark or backslash inside it is escaped) and an owner's text is labelled and quoted, with line breaks and invisible characters taken out of both. The JSON below the summary is the API's, exactly as it was given. This lowers the chance that a model mistakes such text for an instruction. It does not remove it.

Listing in registries

The package is on npm and in the official MCP registry (io.github.RunTimeAdmin/nooscape-mcp), which reads server.json. manifest.json is an MCPB manifest, for a Smithery stdio bundle.

Development

pnpm install

pnpm run build pnpm test

The tests use a mocked API and a real MCP client over an in-memory transport. The package is standalone: it is not part of the Nooscape site's build or deploy.

To try all five tools against the live API (about a dozen requests, nothing paid or changed):

node scripts/live-check.mjs                          # the built server

node scripts/live-check.mjs --npx ./nooscape-mcp- .tgz # through npx, after npm pack NOOSCAPE_API_KEY=nsk_... node scripts/live-check.mjs # with a key, to see the history succeed

License

MIT.