nooscape-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOOSCAPE_API_KEY | No | Optional. An API key, sent as `Authorization: Bearer`. A free key is made at https://nooscape.si/developers/keys. It is never logged, never echoed and never put in a result or an error. Without a key, `search_agents` and `get_agent` still work (30 requests/minute); a free key raises limits to 60/minute and 1,000/day and unlocks `get_agent_history`; `check` needs a Pro key or an x402 payment. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_agentsA | Search the agents Nooscape lists by name, endpoint host, registry key or wallet. Returns up to 10 matches, newest first, each with its chain, id, evidence layer and the dates it was first and last seen. Use get_agent for one agent's full record. |
| get_agentA | What Nooscape has on record about one agent: when it was first and last seen, who registered it, its evidence level, how many other listings share its wallet, its registry activity and ratings, and any claim by its owner (whose own words are labelled as theirs). Every answer says when it was read and where from. Not a review and not a verdict. |
| get_agent_historyA | One agent's registry events (mint, transfers, profile link updates) and the public history of claims on it, each with its date. Needs an API key: set NOOSCAPE_API_KEY (a free key is enough). |
| checkA | Dated facts to read before you pay or rely on an agent, a wallet or an endpoint: when Nooscape first saw each listing, its recorded ownership changes, the share of its ratings that were revoked, how many listings its wallet registered, and the evidence level. Give exactly one of agent, wallet or url. Facts only: there is no score and no verdict. Needs a Pro key or an x402 payment (currently $0.01 per call); this server does not pay, so without a Pro key it explains what is needed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
search_agents (find) vs get_agent (full record) vs get_agent_history (time-series events) vs check (cross-resource risk facts) are mostly distinct. get_agent and check overlap on facts like evidence level, first-seen and ratings, though check's payment-gated, wallet/url-capable framing helps separate them.
search_agents, get_agent, get_agent_history follow a clear verb_noun pattern with a consistent agent subject. The bare verb 'check' is a minor deviation but remains readable and unambiguous in context.
Four tools is on the lean side but well-matched to a read-only agent-intelligence surface: search, detail, history and risk check. Nothing obviously redundant, though it sits near the thin end.
Search, single-record retrieval, historical events and a multi-resource risk check give good coverage of the stated lookup domain. Gaps are minor—no dedicated wallet/endpoint listing tools, but check partly covers those via mix.