# Professor Sausages — On-chain (remote · x402.professorsausages.com)

EVM gas, Chainlink prices, token-safety, swap quotes, ENS, OFAC & NFT via x402.

- Trust score: 73/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `x402.professorsausages.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-professorsausages-sausage-onchain/mcp-onchain.md), [page](https://verifymcp.io/servers/com-professorsausages-sausage-onchain/mcp-onchain)

## Channel facts

- Endpoint: `https://x402.professorsausages.com/mcp/onchain`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-09-21.

- **Endpoint Security**: 46/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 12 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2300 tokens (~191/item across 12 items; 12 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Professor Sausages — On-chain MCP server?

Professor Sausages — On-chain is a hosted endpoint at https://x402.professorsausages.com/mcp/onchain, 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-professorsausages-sausage-onchain 'https://x402.professorsausages.com/mcp/onchain'
```

### Cursor

```json
{
  "mcpServers": {
    "com-professorsausages-sausage-onchain": {
      "url": "https://x402.professorsausages.com/mcp/onchain"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-professorsausages-sausage-onchain": {
      "type": "http",
      "url": "https://x402.professorsausages.com/mcp/onchain"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-professorsausages-sausage-onchain]
url = "https://x402.professorsausages.com/mcp/onchain"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-professorsausages-sausage-onchain": {
      "type": "remote",
      "url": "https://x402.professorsausages.com/mcp/onchain",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-professorsausages-sausage-onchain --url 'https://x402.professorsausages.com/mcp/onchain' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-professorsausages-sausage-onchain:
    url: "https://x402.professorsausages.com/mcp/onchain"
```

### Netclaw

```json
{
  "McpServers": {
    "com-professorsausages-sausage-onchain": {
      "Transport": "http",
      "Url": "https://x402.professorsausages.com/mcp/onchain"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-professorsausages-sausage-onchain -t streamable-http -u 'https://x402.professorsausages.com/mcp/onchain'
```

### Other

```json
{
  "mcpServers": {
    "com-professorsausages-sausage-onchain": {
      "type": "http",
      "url": "https://x402.professorsausages.com/mcp/onchain"
    }
  }
}
```

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-09-14 (score 73, 0)

- [security] Stability: 0.97 → pass

### 2026-09-13 (score 73, +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-09-11 (score 72, +1)

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

### 2026-09-09 (score 71, +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-09-07 (score 70, +1)

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

### 2026-09-05 (score 69, +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.

### 2026-09-03 (score 68, +1)

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

### 2026-09-01 (score 67, +1)

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

## MCP tools (12)

### `find_data` (~103 tokens)

Find the right data source

Describe the data you need in plain language (e.g. 'Apple risk factors 2023', 'is this token a honeypot', 'is this email deliverable', 'read this page'). Searches this server's datasets first, then the whole Professor Sausages catalog, and returns matching endpoints with method, URL, price, and how to call them. Free.

Input parameters:

- `task` (string, required): What you're trying to find or do, in your own words

### `pricing` (~44 tokens)

Price list

Every endpoint this server fronts, with its exact per-call USD price (x402, USDC on Base) and a one-line summary, read live from the route table. Free.

### `request_data` (~110 tokens)

Request missing data

The suggestion box: ask for data we don't have (a pre-2015 filing, an uncovered ticker, an unsupported chain, a whole dataset). Requests feed the nightly ingestion queue — filings are usually available within ~24h. Include contact if you want to hear back. Free.

Input parameters:

- `contact` (string): Optional: URL/email/handle for follow-up
- `description` (string, required): What data you need, in your own words
- `use_case` (string): Optional: what you're building

### `gas_price` (~242 tokens)

Current gas market for a chain

Bid-ready EIP-1559 fees (slow/standard/fast maxFeePerGas + maxPriorityFeePerGas, tx-ready wei) for one chain, read live from public RPCs. Pass tx_type to get the USD cost of that specific transaction instead, including the OP-stack L1 data fee naive estimators miss. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free `pricing` tool lists every price at once.

Input parameters:

- `chain` (string): Which chain's gas market to read.
- `gas` (integer): Optional gas limit override when tx_type is set.
- `speed` (string): Which fee tier to price the estimate at.
- `tx_type` (string): Optional: cost a specific transaction shape rather than returning raw fees.
- `x_payment` (string): Optional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and…

### `gas_compare` (~180 tokens)

Cheapest chain right now

Rank every supported chain by all-in USD transaction cost — the 'where should I send this' routing decision, with the OP-stack L1 data fee included. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free `pricing` tool lists every price at once.

Input parameters:

- `gas` (integer): Optional gas limit override.
- `speed` (string): Fee tier to compare at.
- `tx_type` (string): Transaction shape to price on every chain.
- `x_payment` (string): Optional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and…

### `spot_price` (~224 tokens)

Oracle spot price

Live Chainlink on-chain spot price for an asset (latestRoundData, with round metadata). Pass `to` as well to cross-convert two assets via their USD feeds, with both legs reported. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free `pricing` tool lists every price at once.

Input parameters:

- `amount` (number): Amount to convert (with `to`).
- `asset` (string, required): Asset symbol with a Chainlink feed (call /prices/feeds free to list them).
- `chain` (string): Which chain's oracle to read.
- `to` (string): Optional second asset — converts `asset` into it instead of quoting USD.
- `x_payment` (string): Optional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and…

### `token_safety` (~167 tokens)

Token rug-pull / honeypot check

Heuristic token safety check: follows the proxy and scans the bytecode that actually runs, plus ownership and transfer restrictions. Returns a verdict with per-rule evidence. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free `pricing` tool lists every price at once.

Input parameters:

- `address` (string, required): Token contract address.
- `chain` (string): Which chain the token contract is on.
- `x_payment` (string): Optional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and…

### `address_screen` (~177 tokens)

Screen a crypto address against OFAC

Screen a crypto address against the full live OFAC SDN list, segmented by chain. Returns a verdict with the matching SDN entries as evidence — never a silent all-clear. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free `pricing` tool lists every price at once.

Input parameters:

- `address` (string, required): The address to screen, in that chain's native format.
- `chain` (string): Which chain the address belongs to.
- `x_payment` (string): Optional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and…

### `swap_quote` (~198 tokens)

DEX swap quote

Indicative UniswapV2 swap quote from live on-chain reserves: amount out, execution price, and price impact — what the trade will actually cost before you sign it. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free `pricing` tool lists every price at once.

Input parameters:

- `amount` (number): Amount of token_in to sell.
- `chain` (string): Which chain to quote on.
- `token_in` (string, required): Address of the token being sold.
- `token_out` (string, required): Address of the token being bought.
- `x_payment` (string): Optional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and…

### `ens_resolve` (~233 tokens)

Resolve ENS names and addresses

Resolve an ENS name to an address, or an address to its forward-verified primary name — direction is detected from the input. view='profile' returns the full identity card (multichain addresses, text records, contenthash, avatar); view='avatar' dereferences the avatar to an image URL. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free `pricing` tool lists every price at once.

Input parameters:

- `keys` (string): Comma-separated ENS text-record keys (view='text').
- `query` (string, required): An ENS name (ends in .eth) or a 0x address.
- `view` (string): resolve = name↔address; profile/avatar/text need a name.
- `x_payment` (string): Optional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and…

### `chain_info` (~264 tokens)

EVM chain registry

Canonical record for an EVM chain — name, native currency, explorers, liveness-scored public RPCs. view='rpcs' returns only the ranked, eth_chainId-probed RPC list; view='wallet_config' returns a ready-to-submit EIP-3085 wallet_addEthereumChain object; view='search' finds chains by name or symbol; view='l2s' lists a parent chain's L2s. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free `pricing` tool lists every price at once.

Input parameters:

- `chain_id` (string): Numeric chain id (required for record/rpcs/wallet_config).
- `parent` (string): Parent chain id for view='l2s'.
- `q` (string): Name/symbol fragment (view='search').
- `view` (string): Which shape of chain data to return.
- `x_payment` (string): Optional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and…

### `nft_scam_check` (~203 tokens)

NFT scam / copymint check

Deterministic scam checklist with a verdict and evidence (spam flags, copymint collisions, holder concentration). Pass a collection contract to check the collection, or a wallet to check that wallet's whole scam exposure holding by holding. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free `pricing` tool lists every price at once.

Input parameters:

- `chain` (string): Which chain to read (Ethereum mainnet today).
- `contract` (string): Collection contract address to check.
- `wallet` (string): Wallet address — checks scam exposure across its holdings instead.
- `x_payment` (string): Optional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-professorsausages-sausage-onchain/mcp-onchain#diagnostics

## Score history

- 2026-09-21: 73
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 71
- 2026-09-09: 71
- 2026-09-08: 70
- 2026-09-07: 70
- 2026-09-06: 69
- 2026-09-05: 69
- 2026-09-04: 68
- 2026-09-03: 68
- 2026-09-02: 67
- 2026-09-01: 67
- 2026-08-31: 66
- 2026-08-30: 66
- 2026-08-29: 66
- 2026-08-28: 65
- 2026-08-27: 65
- 2026-08-26: 64
- 2026-08-25: 62
- 2026-08-24: 62
- 2026-08-23: 61

## Common questions

### What is the Professor Sausages — On-chain MCP server?

Professor Sausages — On-chain is an MCP server listed in the public MCP registry as com.professorsausages/sausage-onchain. EVM gas, Chainlink prices, token-safety, swap quotes, ENS, OFAC & NFT via x402. This page covers its hosted endpoint (https://x402.professorsausages.com/mcp/onchain).

### Is the Professor Sausages — On-chain MCP server safe to use?

Professor Sausages — On-chain scores 73 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 Professor Sausages — On-chain MCP server expose?

Professor Sausages — On-chain exposes 12 tools: find_data, pricing, request_data, gas_price, gas_compare, and 7 more. Their descriptions and schemas cost roughly 2,145 tokens of context every time the server is loaded.

### Does the Professor Sausages — On-chain MCP server require authentication?

No. We connected to Professor Sausages — On-chain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Professor Sausages — On-chain MCP server still maintained?

Professor Sausages — On-chain is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://x402.professorsausages.com/mcp/onchain
- Website: https://x402.professorsausages.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-professorsausages-sausage-onchain/mcp-onchain.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-professorsausages-sausage-onchain/mcp-onchain.json
- HTML version of this page: https://verifymcp.io/servers/com-professorsausages-sausage-onchain/mcp-onchain