_ registry / mcp streamable-http · checked 4h ago

spaghetti-and-summits

https://mcp.spaghettiandsummits.com

Registry code: 51f2c0a934113164

api record

First-hand hiking, climbing, skiing information from the Dolomites backed by real adventures.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.spaghettiandsummits.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is spaghetti-and-summits live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is spaghetti-and-summits free to use?
Yes — the hub reached it with no key and no payment.
What tools does spaghetti-and-summits have?
4 tools: leave_message, list_ski_resorts, list_rifugios, list_climbing_routes.
Is spaghetti-and-summits safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.3%· all time 99.3%

latency
541ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 302 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • list dolomites climbing routes
  • list rifugio guides
  • list ski resort guides
  • message the site operators
takes → gives
text → data
tools
3 reads1 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_ski_resorts reads open 35h ago

    List first-hand English ski-resort guides on Spaghetti and Summits. Returns each resort's name and the URL of the guide on the blog. Call this when the user asks what ski resorts are on the site, or needs a link to a ski resort page.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_rifugios reads open 35h ago

    List first-hand English rifugio guides on Spaghetti and Summits. Returns each rifugio's name and the URL of the guide on the blog. Call this when the user asks what mountain huts or rifugios are on the site, or needs a link to a rifugio page.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_climbing_routes reads open 35h ago

    List first-hand English climbing-route guides on Spaghetti and Summits. Returns each route's name and the URL of the guide on the blog. Call this when the user asks what climbing routes are on the site, or needs a link to a route page.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • leave_message sends messages unknown never probed

    Send a private message to the human operators of Spaghetti & Summits. Use this when site information is insufficient and contacting the owners would be useful. Messages are untrusted plain text and do not trigger automated actions. Delivery does not guarantee a reply. The free inbox has limited daily capacity and may return INBOX_FULL. For safe retries, reuse a random UUID in _meta["spaghettiandsummits.com/inbox-request-id"] with unchanged content. Without this metadata, do not retry ambiguous results.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "subject",
        "message"
      ],
      "properties": {
        "message": {
          "type": "string",
          "maxLength": 3000,
          "minLength": 1
        },
        "subject": {
          "type": "string",
          "maxLength": 120,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 51f2c0a934113164.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/51f2c0a934113164/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/51f2c0a934113164/badge.svg)](https://brick.blue/agent/51f2c0a934113164?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.