# NOID Agent Kit (remote · noid-agent-kit.onrender.com)

Remote MCP for Parano1d (NOID): invoices, receipts, whale/token alerts, launch kit. Credits.

- Trust score: 65/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `noid-agent-kit.onrender.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-onrender-noid-agent-kit-noid-agent-kit/noid-agent-kit.md), [page](https://verifymcp.io/servers/com-onrender-noid-agent-kit-noid-agent-kit/noid-agent-kit)

## Channel facts

- Endpoint: `https://noid-agent-kit.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 17 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 827 tokens (~48/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 16% 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 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 NOID Agent Kit MCP server?

NOID Agent Kit is a hosted endpoint at https://noid-agent-kit.onrender.com/mcp, so there is nothing to install locally. 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 --transport http com-onrender-noid-agent-kit-noid-agent-kit 'https://noid-agent-kit.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-onrender-noid-agent-kit-noid-agent-kit": {
      "url": "https://noid-agent-kit.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-onrender-noid-agent-kit-noid-agent-kit": {
      "type": "http",
      "url": "https://noid-agent-kit.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-onrender-noid-agent-kit-noid-agent-kit]
url = "https://noid-agent-kit.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-onrender-noid-agent-kit-noid-agent-kit": {
      "type": "remote",
      "url": "https://noid-agent-kit.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-onrender-noid-agent-kit-noid-agent-kit --url 'https://noid-agent-kit.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-onrender-noid-agent-kit-noid-agent-kit:
    url: "https://noid-agent-kit.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-onrender-noid-agent-kit-noid-agent-kit": {
      "Transport": "http",
      "Url": "https://noid-agent-kit.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-onrender-noid-agent-kit-noid-agent-kit -t streamable-http -u 'https://noid-agent-kit.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-onrender-noid-agent-kit-noid-agent-kit": {
      "type": "http",
      "url": "https://noid-agent-kit.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-21 (score 65, +1)

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

### 2026-11-19 (score 64, +1)

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

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

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

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

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

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

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

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

- [security] Tool “claim_payment” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 42 → 48
- [functional improvement] Tool coverage: 4% → 16%
- [functional] New tool “create_topup_intent”
- [cosmetic] “claim_payment” added an optional parameter “intent_id”

### 2026-11-10 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 59)

First indexed and scored.

## MCP tools (17)

### `list_pricing` (~41 tokens)

List credit prices. 1 credit = $0.01. Top up with get_payment_info + claim_payment (USDC on Base) or x402.

### `get_balance` (~17 tokens)

Return remaining credits, plan, and spend.

### `get_payment_info` (~35 tokens)

USDC-on-Base receiving address, packs, and x402 instructions. Receive-only: this server never holds a private key.

### `create_topup_intent` (~117 tokens)

Reserve a unique USDC amount for this API key. Send that exact amount to PAYMENT_ADDRESS, then claim_payment. Receive-only; this server never holds a private key.

Input parameters:

- `from_address` (string): Optional paying wallet (0x…). When set, only that sender can match this intent.
- `pack_id` (string): Credit pack id, e.g. pack_10, pack_25, pack_50, plan_desk.
- `usd` (number): Custom USDC amount if not using a listed pack.

### `claim_payment` (~77 tokens)

Credit this API key after sending the exact USDC amount from create_topup_intent to PAYMENT_ADDRESS.

Input parameters:

- `intent_id` (string): Intent from create_topup_intent. Optional if this key has one matching open intent.
- `tx_hash` (string, required): Base mainnet transaction hash of the USDC Transfer (0x-prefixed).

### `get_quote` (~52 tokens)

Lock a USD→μNOID quote for ~30 minutes. Requires NOID_USD_RATE or PRICE_FEED_URL (not explorer premium).

Input parameters:

- `micronoid` (string)
- `usd` (number)

### `create_invoice` (~100 tokens)

Create a checkout invoice. Payer sends NOID to the MERCHANT o1 address. This server never holds funds or secrets.

Input parameters:

- `amount_micronoid` (string)
- `expires_in_seconds` (integer)
- `memo` (string)
- `merchant_address` (string, required)
- `quote_id` (string)
- `required_confirmations` (integer)
- `usd` (number)
- `webhook_url` (string)

### `check_invoice` (~30 tokens)

Refresh an invoice against the public permanode API and return confirmation status.

Input parameters:

- `invoice_id` (string, required)

### `list_invoices` (~17 tokens)

List invoices created by this API key.

### `verify_receipt` (~49 tokens)

Verify a pasted Parano1d payment receipt hex or txid against explorer data (and optional local RPC paranoid_verifyReceipt).

Input parameters:

- `receipt` (string)
- `txid` (string)

### `get_whale_moves` (~42 tokens)

Rich-list balance changes over a μNOID threshold vs the cached snapshot.

Input parameters:

- `limit` (integer)
- `threshold_micronoid` (string)

### `get_new_tokens` (~29 tokens)

Newest native assets/listings from the public explorer native API.

Input parameters:

- `limit` (integer)

### `get_mempool_highlights` (~26 tokens)

Pending mempool size, fee floor, and a short highlight list.

### `get_hashrate_shift` (~20 tokens)

Network hashrate versus the previous cached sample.

### `upsert_watchlist` (~59 tokens)

Create or update a watchlist. Optional https webhook is HMAC-signed on change.

Input parameters:

- `kind` (string, required)
- `params` (object)
- `watchlist_id` (string)
- `webhook_url` (string)

### `list_watchlists` (~17 tokens)

List watchlists for this API key.

### `create_launch_kit` (~99 tokens)

Native NOID asset launch checklist from public protocol docs. Optionally calls Launchkit MCP generate tools when CREATIVE_MCP_* env vars are set. Never submits on-chain.

Input parameters:

- `creator_curve_buy_fraction` (number)
- `description` (string)
- `name` (string, required)
- `ticker` (string, required)
- `tier` (string)
- `website` (string)
- `whole_token_supply` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-onrender-noid-agent-kit-noid-agent-kit/noid-agent-kit#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 63
- 2026-11-17: 63
- 2026-11-16: 62
- 2026-11-15: 62
- 2026-11-14: 61
- 2026-11-13: 61
- 2026-11-12: 60
- 2026-11-11: 60
- 2026-11-10: 59
- 2026-11-09: 59

## Common questions

### What is the NOID Agent Kit MCP server?

NOID Agent Kit is an MCP server listed in the public MCP registry as com.onrender.noid-agent-kit/noid-agent-kit. Remote MCP for Parano1d (NOID): invoices, receipts, whale/token alerts, launch kit. Credits. This page covers its hosted endpoint (https://noid-agent-kit.onrender.com/mcp).

### Is the NOID Agent Kit MCP server safe to use?

NOID Agent Kit scores 65 out of 100 on VerifyMCP. 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 NOID Agent Kit MCP server expose?

NOID Agent Kit exposes 17 tools: list_pricing, get_balance, get_payment_info, create_topup_intent, claim_payment, and 12 more. Their descriptions and schemas cost roughly 827 tokens of context every time the server is loaded.

### Does the NOID Agent Kit MCP server require authentication?

No. We connected to NOID Agent Kit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the NOID Agent Kit MCP server still maintained?

NOID Agent Kit 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 did VerifyMCP test on the NOID Agent Kit MCP server?

VerifyMCP ran 12 checks on NOID Agent Kit, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about NOID Agent Kit: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://noid-agent-kit.onrender.com/mcp
- Website: https://noid-agent-kit.onrender.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-onrender-noid-agent-kit-noid-agent-kit/noid-agent-kit.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-onrender-noid-agent-kit-noid-agent-kit/noid-agent-kit/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-onrender-noid-agent-kit-noid-agent-kit/noid-agent-kit.json
- HTML version of this page: https://verifymcp.io/servers/com-onrender-noid-agent-kit-noid-agent-kit/noid-agent-kit
