Is the Professorsausages Sausage Trust MCP server down?

mcp-registry/com.professorsausages/sausage-trust · v1.0.0

healthy
Last checked 2026-10-25 21:25 UTC · handshake 43ms

As of 2026-10-25 21:25 UTC, the Professorsausages Sausage Trust MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,835
outages (90d)
0
tools
12

Email, phone, domain, URL & OFAC verification; phishing and IBAN checks via x402.

Install Professorsausages Sausage Trust MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http professorsausages-sausage-trust-mcp-serv https://x402.professorsausages.com/mcp/trust

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "professorsausages-sausage-trust-mcp-serv": {
      "type": "http",
      "url": "https://x402.professorsausages.com/mcp/trust"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 12 tool(s); ~2,958 tokens of tool definitions.
Scores higher than 45% of 15,723 MCP servers Glimind has audited.
Its tool list costs an agent ~2,958 tokens per session — more than 50% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: address_screen, domain_intel, email_check, find_data, iban_check and 7 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.professorsausages%2Fsausage-trust/fixes

address_screen 1 change
{
  "name": "address_screen",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "address"
    ],
    "properties": {
      "chain": {
        "enum": [
          "base",
          "ethereum",
          "bitcoin",
          "tron",
          "litecoin",
          "monero",
          "dash",
          "zcash",
          "bitcoin-cash",
          "dogecoin",
          "bitcoin-gold",
          "verge",
          "solana"
        ],
        "type": "string",
        "default": "base",
        "examples": [
          "base"
        ],
        "description": "Which chain the address belongs to."
      },
      "address": {
        "type": "string",
        "examples": [
          "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
        ],
        "description": "The address to screen, in that chain's native format."
      },
      "x_payment": {
        "type": "string",
        "description": "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 get the data."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Screen a crypto address against OFAC"
}
email_check 1 change
{
  "name": "email_check",
  "description": "Deliverability signals for one address: RFC5322 syntax, live MX/SPF/DMARC over DNS-over-HTTPS, disposable/role-account flags. Signals with evidence — not a guaranteed inbox verdict. 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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "email"
    ],
    "properties": {
      "email": {
        "type": "string",
        "examples": [
          "[email protected]"
        ],
        "description": "The address to check."
      },
      "x_payment": {
        "type": "string",
        "description": "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 get the data."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Email deliverability signals"
}
find_data 1 change
{
  "name": "find_data",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "task"
    ],
    "properties": {
      "task": {
        "type": "string",
        "examples": [
          "Apple risk factors 2023"
        ],
        "description": "What you're trying to find or do, in your own words"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Find the right data source"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.professorsausages/sausage-trust"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.professorsausages/sausage-trust"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.professorsausages%2Fsausage-trust.svg)](https://glimind.com/server/mcp-registry%2Fcom.professorsausages%2Fsausage-trust?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.professorsausages%2Fsausage-trust?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.professorsausages%2Fsausage-trust.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.professorsausages%2Fsausage-trust.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.professorsausages%2Fsausage-trust?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c655f9d90fd7e859…, first seen 2026-10-17, included at leaf 9838 of 68,660. Version history · verify what your client received.

Tools (12)

Compare: most reliable security servers · most reliable email servers · most reliable search servers · most reliable data servers · most reliable communication servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Professorsausages Sausage Trust MCP server down right now?

As of 2026-10-25 21:25 UTC, the Professorsausages Sausage Trust MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Professorsausages Sausage Trust MCP server provide?

Professorsausages Sausage Trust MCP server advertises 12 tools, including address_screen, domain_intel, email_check, find_data, iban_check.

How do I install Professorsausages Sausage Trust MCP server?

Point your MCP client at this streamable-http endpoint: https://x402.professorsausages.com/mcp/trust

Is the Professorsausages Sausage Trust MCP server safe to connect to an AI agent?

Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Professorsausages Sausage Trust MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve