Lets an AI assistant query read-only public records about AI agents, crypto wallets, and endpoints to verify history and ownership before interacting.
Also known as RunTimeAdmin/nooscape-mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.6.0
- Last commit
- Nov 2, 2026
- License
- MIT
What is Nooscape MCP?
Nooscape lets an AI assistant query read-only public records about AI agents, crypto wallets, and endpoints to verify history and ownership before interacting.
Summary generated from the project's README
About Nooscape MCP server
Verifying the history and ownership of AI agents, crypto wallets, and endpoints is what nooscape-mcp enables for developers and AI agents. By acting as a read-only client for the Nooscape API, this server provides factual data from public records across multiple blockchains, including Ethereum, Solana, Base, BNB Smart Chain, Monad, Arc, and Robinhood Chain. It allows an AI assistant to perform pre-flight checks on a wallet or URL to see recorded ownership changes and evidence levels before any transaction occurs.
Users can run the server locally using npx or connect it to clients like Claude Desktop, Cursor, or Claude Code. While basic searches and agent lookups work without authentication, a free API key increases rate limits and enables access to agent history. For the most detailed pre-flight facts via the check tool, a Pro key or an x402 payment is required. The server is designed to be a thin layer that returns plain summaries alongside exact JSON data, ensuring that every piece of information includes its source and evidence level.
What you can do with it
- 1Verify agent registration detailsAn AI assistant can look up when a specific agent on the Robinhood Chain was first seen and identify its registrant.
- 2Perform pre-flight wallet checksA developer can ask an AI to investigate a wallet's history and ownership changes before sending funds.
- 3Audit agent registry eventsYou can retrieve the public history of claims and registry events for a specific agent ID.
- 4Monitor directory statisticsAn AI can report on how many entries are listed on various chains and when they were last indexed.
Written from the project's README. Every use case is checked against a quote from it.
How to install Nooscape MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Nooscape MCP in Claude Code
$ claude mcp add --env 'NOOSCAPE_API_KEY=<YOUR_NOOSCAPE_API_KEY>' nooscape-mcp -- npx -y nooscape-mcpInstall Nooscape MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"nooscape-mcp": {
"command": "npx",
"args": [
"-y",
"nooscape-mcp"
],
"env": {
"NOOSCAPE_API_KEY": "<YOUR_NOOSCAPE_API_KEY>"
}
}
}
}Install Nooscape MCP in VS Code
.vscode/mcp.json
{
"servers": {
"nooscape-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nooscape-mcp"
],
"env": {
"NOOSCAPE_API_KEY": "<YOUR_NOOSCAPE_API_KEY>"
}
}
}
}Install Nooscape MCP in VS Code CLI
$ code --add-mcp '{"name":"nooscape-mcp","type":"stdio","command":"npx","args":["-y","nooscape-mcp"],"env":{"NOOSCAPE_API_KEY":"<YOUR_NOOSCAPE_API_KEY>"}}'Install Nooscape MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"nooscape-mcp": {
"command": "npx",
"args": [
"-y",
"nooscape-mcp"
],
"env": {
"NOOSCAPE_API_KEY": "<YOUR_NOOSCAPE_API_KEY>"
}
}
}
}Install Nooscape MCP in Codex
$ codex mcp add nooscape-mcp --env 'NOOSCAPE_API_KEY=<YOUR_NOOSCAPE_API_KEY>' -- npx -y nooscape-mcpInstall Nooscape MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.nooscape-mcp] command = "npx" args = ["-y", "nooscape-mcp"] [mcp_servers.nooscape-mcp.env] NOOSCAPE_API_KEY = "<YOUR_NOOSCAPE_API_KEY>"
Install Nooscape MCP in Gemini CLI
$ gemini mcp add -s user -e 'NOOSCAPE_API_KEY=<YOUR_NOOSCAPE_API_KEY>' nooscape-mcp npx -- -y nooscape-mcpInstall Nooscape MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"nooscape-mcp": {
"command": "npx",
"args": [
"-y",
"nooscape-mcp"
],
"env": {
"NOOSCAPE_API_KEY": "<YOUR_NOOSCAPE_API_KEY>"
}
}
}
}Configuration
NOOSCAPE_API_KEYSecretOptional. A Nooscape API key, sent as a bearer token. A free key opens the agent history; the pre-flight check needs a Pro key. Make one at https://nooscape.si/developers/keys.
| Name | Description | |
|---|---|---|
| NOOSCAPE_API_KEY | Optional. A Nooscape API key, sent as a bearer token. A free key opens the agent history; the pre-flight check needs a Pro key. Make one at https://nooscape.si/developers/keys. | Secret |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableruntimeadmin/nooscape-mcp is public and reachablegithub.com/runtimeadmin/nooscape-mcp ↗Pass
- Package names this repository as its sourcenooscape-mcp names runtimeadmin/nooscape-mcp as sourcenpmjs.com/package/nooscape-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-02github.com/runtimeadmin/nooscape-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from nooscape-mcpPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubnooscape-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.
| Tool | What it does | Needs |
|---|---|---|
search_agents(query, chain?) |
Search listed agents by name, endpoint host, registry key or wallet. | nothing |
get_stats() |
What the directory holds on each chain it reads: the entries it lists and the registries behind them, the ratings recorded on chain where they are counted, the entries first seen in the last 24 hours, and when each chain was last read. A chain Nooscape does not read is reported as not indexed, which is not zero. | nothing |
get_agent(chain, id) |
One agent's record: first and last seen, who registered it, evidence level, listings that share its wallet, registry activity, ratings, and any claim by its owner. | nothing |
get_agent_history(chain, id) |
One agent's registry events and the public history of claims on it. | an API key (a free one is enough) |
check(agent | wallet | url) |
Pre-flight facts: when each listing was first seen, recorded ownership changes, the share of ratings that were revoked, how many listings its wallet registered, and the evidence level. | a Pro key, or an x402 payment (see below) |
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
| Variable | What it is |
|---|---|
NOOSCAPE_API_KEY |
Optional. An API key, sent as Authorization: Bearer. A free key is made at nooscape.si/developers/keys. It is never logged, never echoed and never put in a result or an error. |
NOOSCAPE_MCP_TOKEN |
Optional, and only for --http. A shared secret of at least 24 characters. Required with --allow-remote; whenever it is set, every caller must send it as Authorization: Bearer <secret>. It is never logged or echoed. |
Keys, limits and payment
- No key:
search_agents,get_agentandget_statswork, 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. checkneeds 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,checkreturns 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.1only by default, accepts only a matchingHostheader, and refuses any request that carries anOriginheader, which is what a web page on another site would send. - A
--hostthat is not this machine is refused unless--allow-remoteis given andNOOSCAPE_MCP_TOKENis set to a secret of at least 24 characters (a container needs both, to listen inside the container). Every request must then carry it asAuthorization: Bearer <secret>, 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 withopenssl rand -hex 24. Off this machine theHostandOriginchecks 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_KEYand 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.siand 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-<version>.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.
Nooscape MCP questions
How do I add Nooscape MCP to Claude Code?
Run claude mcp add --env 'NOOSCAPE_API_KEY=<YOUR_NOOSCAPE_API_KEY>' nooscape-mcp -- npx -y nooscape-mcp in your terminal. Add --scope user to make it available in every project.
How do I add Nooscape MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What chains are supported by Nooscape?
Supported chains include Robinhood Chain, BNB Smart Chain, Solana, Ethereum, Base, Arc, and Monad.
Do I need an API key to use the search tools?
No, lookups and searches work without a key, though a free key increases rate limits and enables history access.
Is the information provided a verdict on whether an agent is safe?
No, the server provides facts and dates but does not review, rank, or provide a verdict on whether an agent is good or bad.