# io.github.RunTimeAdmin/nooscape-mcp (npm · nooscape-mcp)

Read-only facts with dates about AI agents, wallets and endpoints from Nooscape's public record.

- Trust score: 82/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `nooscape-mcp`: 82/100 (this document), [markdown](https://verifymcp.io/servers/runtimeadmin-nooscape-mcp/nooscape-mcp.md), [page](https://verifymcp.io/servers/runtimeadmin-nooscape-mcp/nooscape-mcp)

## Channel facts

- Registry: `npm`
- Package: `nooscape-mcp`
- Version: `0.6.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 951 tokens (~190/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.RunTimeAdmin/nooscape-mcp server?

io.github.RunTimeAdmin/nooscape-mcp runs locally as an npm package, launched with npx -y nooscape-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add runtimeadmin-nooscape-mcp -- npx -y nooscape-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "runtimeadmin-nooscape-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "nooscape-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "runtimeadmin-nooscape-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "nooscape-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add runtimeadmin-nooscape-mcp -- npx -y nooscape-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "runtimeadmin-nooscape-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "nooscape-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add runtimeadmin-nooscape-mcp --command npx --arg -y --arg nooscape-mcp
```

### Hermes

```yaml
mcp_servers:
  runtimeadmin-nooscape-mcp:
    command: "npx"
    args: ["-y", "nooscape-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "runtimeadmin-nooscape-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "nooscape-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add runtimeadmin-nooscape-mcp -t stdio -c npx -a -y nooscape-mcp
```

### Other

```json
{
  "mcpServers": {
    "runtimeadmin-nooscape-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "nooscape-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-18 (score 82, 0)

- [security] Stability: 0.97 → pass

### 2026-11-17 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 81, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-14 (score 80, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-13 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-11 (score 79, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-09 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `search_agents` (~119 tokens)

Search Nooscape agents

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.

Input parameters:

- `chain` (string): The chain: robinhood, bnb, solana, ethereum, base, arc or monad.
- `query` (string, required): A name, an endpoint host, a registry key or a wallet address. Two to 64 characters.

### `get_stats` (~105 tokens)

What the directory holds

Counts of what Nooscape's 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, how many entries were 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. A count of listed entries is not a count of the agents that exist or work. Needs no key.

### `get_agent` (~177 tokens)

Get one agent's record

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.

Input parameters:

- `chain` (string, required): The chain: robinhood, bnb, solana, ethereum, base, arc or monad.
- `id` (string, required): The agent's id on its registry: the token id (digits) on robinhood, bnb, ethereum, base, arc and monad, the address on solana.
- `registry` (string): Solana only, when more than one registry lists the address (the answer then names them).

### `get_agent_history` (~149 tokens)

Get one agent's history

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).

Input parameters:

- `chain` (string, required): The chain: robinhood, bnb, solana, ethereum, base, arc or monad.
- `id` (string, required): The agent's id on its registry: the token id (digits) on robinhood, bnb, ethereum, base, arc and monad, the address on solana.
- `registry` (string): Solana only, when more than one registry lists the address (the answer then names them).

### `check` (~210 tokens)

Pre-flight check

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.

Input parameters:

- `agent` (object): One agent, by chain and id.
- `chain` (string): Narrows a wallet or a url to one chain. Do not give it with agent.
- `url` (string): An endpoint address or a bare host (example.com): the listings that name that host. Nothing is fetched from it.
- `wallet` (string): A wallet address (0x... or a Solana address): the listings it registered.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/runtimeadmin-nooscape-mcp/nooscape-mcp#diagnostics

## Score history

- 2026-11-21: 82
- 2026-11-20: 82
- 2026-11-19: 82
- 2026-11-18: 82
- 2026-11-17: 82
- 2026-11-16: 81
- 2026-11-15: 81
- 2026-11-14: 80
- 2026-11-13: 80
- 2026-11-12: 79
- 2026-11-11: 79
- 2026-11-10: 78
- 2026-11-09: 78
- 2026-11-08: 77
- 2026-11-07: 77
- 2026-11-06: 76
- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 57
- 2026-10-27: 57
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 70
- 2026-10-23: 70

## Common questions

### What is the io.github.RunTimeAdmin/nooscape-mcp server?

io.github.RunTimeAdmin/nooscape-mcp is listed in the public MCP registry as io.github.RunTimeAdmin/nooscape-mcp. Read-only facts with dates about AI agents, wallets and endpoints from Nooscape's public record. This page covers its npm package (nooscape-mcp).

### Is the io.github.RunTimeAdmin/nooscape-mcp server safe to use?

io.github.RunTimeAdmin/nooscape-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.RunTimeAdmin/nooscape-mcp server expose?

io.github.RunTimeAdmin/nooscape-mcp exposes 5 tools: search_agents, get_stats, get_agent, get_agent_history, check. Their descriptions and schemas cost roughly 760 tokens of context every time the server is loaded.

### Is the io.github.RunTimeAdmin/nooscape-mcp server still maintained?

io.github.RunTimeAdmin/nooscape-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.RunTimeAdmin/nooscape-mcp server under?

io.github.RunTimeAdmin/nooscape-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.RunTimeAdmin/nooscape-mcp server?

VerifyMCP ran 16 checks on io.github.RunTimeAdmin/nooscape-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/nooscape-mcp
- Socket report: https://socket.dev/npm/package/nooscape-mcp
- Repository: https://github.com/RunTimeAdmin/nooscape-mcp
- Changelog RSS feed: https://verifymcp.io/servers/runtimeadmin-nooscape-mcp/nooscape-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/runtimeadmin-nooscape-mcp/nooscape-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/runtimeadmin-nooscape-mcp/nooscape-mcp.json
- HTML version of this page: https://verifymcp.io/servers/runtimeadmin-nooscape-mcp/nooscape-mcp
