Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Professor Sausages — On-chain

REMOTE · X402.PROFESSORSAUSAGES.COM

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

0 this week 73 Trust /100

Last scanned (7 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 0
    • HTTPS: unverified → fail ▼ security
  • 14 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Aug 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://x402.professorsausages.com/mcp/onchain

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=professorsausages.com CN=WE1,O=Google Trust Services,C=US 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA256 d1cf008402c61bd30e0afb661870c9e5
SANs: professorsausages.com, x402.professorsausages.com, *.x402.professorsausages.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of x402.professorsausages.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
professorsausages.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402.professorsausages.com/mcp/onchain Verified 200
http (plaintext) http://x402.professorsausages.com/mcp/onchain Served over HTTP 200
MCP tools · 12 exposed · ~2,145 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
address_screen ~177

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.

NameTypeReqDescription
addressstringyesThe address to screen, in that chain's native format.
chainstring–Which chain the address belongs to.
x_paymentstring–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…

No output schema declared.

No examples provided.

chain_info ~264

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.

NameTypeReqDescription
chain_idstring–Numeric chain id (required for record/rpcs/wallet_config).
parentstring–Parent chain id for view='l2s'.
qstring–Name/symbol fragment (view='search').
viewstring–Which shape of chain data to return.
x_paymentstring–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…

No output schema declared.

No examples provided.

ens_resolve ~233

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.

NameTypeReqDescription
keysstring–Comma-separated ENS text-record keys (view='text').
querystringyesAn ENS name (ends in .eth) or a 0x address.
viewstring–resolve = name↔address; profile/avatar/text need a name.
x_paymentstring–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…

No output schema declared.

No examples provided.

find_data ~103

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.

NameTypeReqDescription
taskstringyesWhat you're trying to find or do, in your own words

No output schema declared.

No examples provided.

gas_compare ~180

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.

NameTypeReqDescription
gasinteger–Optional gas limit override.
speedstring–Fee tier to compare at.
tx_typestring–Transaction shape to price on every chain.
x_paymentstring–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…

No output schema declared.

No examples provided.

gas_price ~242

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.

NameTypeReqDescription
chainstring–Which chain's gas market to read.
gasinteger–Optional gas limit override when tx_type is set.
speedstring–Which fee tier to price the estimate at.
tx_typestring–Optional: cost a specific transaction shape rather than returning raw fees.
x_paymentstring–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…

No output schema declared.

No examples provided.

nft_scam_check ~203

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.

NameTypeReqDescription
chainstring–Which chain to read (Ethereum mainnet today).
contractstring–Collection contract address to check.
walletstring–Wallet address — checks scam exposure across its holdings instead.
x_paymentstring–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…

No output schema declared.

No examples provided.

pricing ~44

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_data ~110

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.

NameTypeReqDescription
contactstring–Optional: URL/email/handle for follow-up
descriptionstringyesWhat data you need, in your own words
use_casestring–Optional: what you're building

No output schema declared.

No examples provided.

spot_price ~224

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.

NameTypeReqDescription
amountnumber–Amount to convert (with `to`).
assetstringyesAsset symbol with a Chainlink feed (call /prices/feeds free to list them).
chainstring–Which chain's oracle to read.
tostring–Optional second asset — converts `asset` into it instead of quoting USD.
x_paymentstring–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…

No output schema declared.

No examples provided.

swap_quote ~198

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.

NameTypeReqDescription
amountnumber–Amount of token_in to sell.
chainstring–Which chain to quote on.
token_instringyesAddress of the token being sold.
token_outstringyesAddress of the token being bought.
x_paymentstring–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…

No output schema declared.

No examples provided.

token_safety ~167

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.

NameTypeReqDescription
addressstringyesToken contract address.
chainstring–Which chain the token contract is on.
x_paymentstring–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…

No output schema declared.

No examples provided.

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.

remote · x402.professorsausages.com

# add to Claude Code
claude mcp add --transport http com-professorsausages-sausage-onchain 'https://x402.professorsausages.com/mcp/onchain'
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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.