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

nanukamachi

https://www.nanukamachi.com

Registry code: 2a469bafea304af3

api record

Public read-only tools for Nanukamachi-dori in Aizuwakamatsu, Japan. Use list-spots, list-parking, or search-archives to find items, then get-spot, get-parking, or get-archive for details. Japanese is the primary language; pass locale=zh-TW for Traditional Chinese.

endpoint
https://www.nanukamachi.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 nanukamachi live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is nanukamachi free to use?
Yes — the hub reached it with no key and no payment.
What tools does nanukamachi have?
7 tools: list-parking, get-site-info, list-spots, search-archives, get-archive, get-parking, get-spot.
Is nanukamachi 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 100%· all time 100%

latency
386ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 7 tools
3 open 4 never probed 3 of 7 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.

  • get-archive open 1h ago

    Get full details for one digital archive item by slug or name, including full description, category, date, and image URL. Use offset and maxChars to page through long descriptions.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Archive item name."
    },
    "slug": {
      "type": "string",
      "description": "Archive slug, e.g. wakamatsushi_nanukamachi_dori."
    },
    "locale": {
      "enum": [
        "ja",
        "zh-TW"
      ],
      "type": "string",
      "default": "ja",
      "description": "Content language. Defaults to Japanese."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "minimum": 0,
      "description": "Start offset for the description. Use nextOffset to continue."
    },
    "maxChars": {
      "type": "integer",
      "maximum": 50000,
      "minimum": 1,
      "description": "Maximum characters to return. Omit to return the full description."
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • get-parking open 1h ago

    Get full details for one parking lot by slug or name, including fee, hours, surface, coordinates, and canonical URL. Use offset and maxChars to page through long descriptions.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Parking lot name."
    },
    "slug": {
      "type": "string",
      "description": "Parking slug, e.g. timesb-sakagami."
    },
    "locale": {
      "enum": [
        "ja",
        "zh-TW"
      ],
      "type": "string",
      "default": "ja",
      "description": "Content language. Defaults to Japanese."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "minimum": 0,
      "description": "Start offset for the description. Use nextOffset to continue."
    },
    "maxChars": {
      "type": "integer",
      "maximum": 50000,
      "minimum": 1,
      "description": "Maximum characters to return. Omit to return the full description."
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • get-spot open 1h ago

    Get full details for one spot on Nanukamachi-dori by slug or name. Returns the full description by default; use offset and maxChars to page through long articles. descriptionTruncated and nextOffset indicate whether more text remains.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Spot name, e.g. とんかつ大将."
    },
    "slug": {
      "type": "string",
      "description": "Spot slug, e.g. tonkatsu-taisyo."
    },
    "locale": {
      "enum": [
        "ja",
        "zh-TW"
      ],
      "type": "string",
      "default": "ja",
      "description": "Content language. Defaults to Japanese."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "minimum": 0,
      "description": "Start offset for the description. Use nextOffset to continue."
    },
    "maxChars": {
      "type": "integer",
      "maximum": 50000,
      "minimum": 1,
      "description": "Maximum characters to return. Omit to return the full description."
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • list-parking unknown never probed

    Search parking lots near Nanukamachi-dori. Returns slug, name, fee, available time, category, and short summary.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum number of results (1-50)."
    },
    "query": {
      "type": "string",
      "description": "Free-text keyword."
    },
    "locale": {
      "enum": [
        "ja",
        "zh-TW"
      ],
      "type": "string",
      "default": "ja",
      "description": "Content language. Defaults to Japanese."
    },
    "category": {
      "enum": [
        "car",
        "bus"
      ],
      "type": "string",
      "description": "car for regular vehicles, bus for bus parking."
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
  • get-site-info unknown never probed

    Get an overview of Nanukamachi.com, its languages, main routes, and machine-readable discovery documents.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list-spots unknown never probed

    Search shops, restaurants, cafes, sights, and accommodation on Nanukamachi-dori. Returns slugs, names, categories, tags, and short summaries.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "genre": {
      "enum": [
        "eat",
        "tabe",
        "miru",
        "yado"
      ],
      "type": "string",
      "description": "eat/tabe = restaurants and cafes, miru = sights and shops, yado = accommodation."
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum number of results (1-50)."
    },
    "query": {
      "type": "string",
      "description": "Free-text keyword in Japanese or Traditional Chinese."
    },
    "locale": {
      "enum": [
        "ja",
        "zh-TW"
      ],
      "type": "string",
      "default": "ja",
      "description": "Content language. Defaults to Japanese."
    },
    "category": {
      "type": "string",
      "description": "Optional data category such as japanesefood, western, ramen, gift, history, building, or antique."
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
  • search-archives unknown never probed

    Search digitized historical postcards and printed materials from Nanukamachi-dori. Returns slug, name, category, date, and short description.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum number of results (1-50)."
    },
    "query": {
      "type": "string",
      "description": "Free-text keyword."
    },
    "locale": {
      "enum": [
        "ja",
        "zh-TW"
      ],
      "type": "string",
      "default": "ja",
      "description": "Content language. Defaults to Japanese."
    },
    "category": {
      "enum": [
        "postcard_single",
        "postcard_set",
        "printed"
      ],
      "type": "string",
      "description": "Archive category."
    }
  },
  "additionalProperties": false
}
    arguments 35 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 2a469bafea304af3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2a469bafea304af3/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/2a469bafea304af3/badge.svg)](https://brick.blue/agent/2a469bafea304af3?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
100%

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.