_ registry / mcp streamable-http · checked 34m ago

soracom-knowledge

https://knowledge-mcp.soracom.com

Registry code: 5ee4b3c1f2167b03

api record

Tools for searching Soracom documentation.

- search_soracom_docs: service guides, console how-tos, service overviews/pricing, IoT recipes.

endpoint
https://knowledge-mcp.soracom.com
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 soracom-knowledge live?
Yes — it answered the hub's last check (checked 34m ago). It answered 100% of checks over the last 30 days.
Is soracom-knowledge free to use?
Yes — the hub reached it with no key and no payment.
What tools does soracom-knowledge have?
3 tools: get_document, search_soracom_docs, search_api_docs.
Is soracom-knowledge 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.6%· all time 99.6%

latency
1,202ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 276 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • search iot platform service guides
  • search api and cli references
  • fetch a documentation page
takes → gives
text → text
tools
3 reads
note
documentation mirror
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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_document reads unknown 4h ago

    Fetch full markdown for a SORACOM documentation page. Also resolves API schema links. Exact URLs are attempted first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "pattern": "^(http://|https://)",
          "maxLength": 2048,
          "description": "A search-result URL, or the full URL of a `#/schema/<Name>` link from search_api_docs. Must start with http:// or https://; pass it exactly as returned."
        }
      }
    }
    arguments 14 lines
  • search_soracom_docs reads unknown 4h ago

    Search SORACOM service documentation, guides, and console how-to articles (user site, service overviews and pricing, IoT recipes). Covers SORACOM services, subscription plans, User Console operations, changelogs, blogs, devices, IoT Store, partners, contract terms, and use cases. Use search_api_docs for API references, CLI commands, or SAM permissions.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 1000,
          "description": "Search query in natural language related to SORACOM services or console usage"
        },
        "market": {
          "enum": [
            "Global",
            "Japan"
          ],
          "type": "string",
          "description": "End-user's deployment market, not the query language. Omit if unknown."
        },
        "language": {
          "enum": [
            "English",
            "Japanese"
          ],
          "type": "string",
          "description": "Documentation language. Omit to auto-detect; set only to pin one language. This does not imply the user's market — use market for that."
        },
        "max_results": {
          "type": "integer",
          "default": 16,
          "maximum": 32,
          "minimum": 1,
          "description": "Maximum results to return (1-32). Increase when exploring."
        },
        "search_mode": {
          "enum": [
            "hybrid",
            "keyword",
            "semantic"
          ],
          "type": "string",
          "default": "hybrid",
          "description": "Search strategy: 'hybrid' combines keyword and vector search; 'keyword' matches exact tokens; 'semantic' uses vector similarity only."
        },
        "document_names": {
          "type": "array",
          "items": {
            "enum": [
              "blog.soracom.com",
              "changelog.soracom.io",
              "changelog.soracom.io/ja",
              "developers.soracom.io",
              "docs.soracom.io",
              "iot-template-gallery.soracom.io",
              "iot-template-gallery.soracom.jp",
              "iot-usecase.com",
              "soracom.io",
              "soracom.io/terms",
              "soracom.jp/iot-recipes",
              "soracom.jp/iot_basics",
              "soracom.jp/partners",
              "soracom.jp/services",
              "soracom.jp/store",
              "soracom.jp/support_partners/certified_device",
              "soracom.jp/terms",
              "support.soracom.io/hc/en-us",
              "support.soracom.io/hc/ja",
              "users.soracom.io"
            ],
            "type": "string"
          },
          "description": "Optional document-name scope filter. Omit when unsure; narrowing too early can hide relevant results. Each document has a fixed language; only in-scope languages are searched. Available documents:\n- blog.soracom.com (Japanese): Official blog: announcements, tutorials, event reports, and customer stories.\n- changelog.soracom.io (English): New feature releases, end-of-service notices, and pricing/spec changes.\n- changelog.soracom.io/ja (Japanese): New feature releases, end-of-service notices, and pricing/spec changes.\n- developers.soracom.io (English): SORACOM Developer Site docs.\n- docs.soracom.io (English): SORACOM Documentation: services, devices, guides, and developer resources.\n- iot-template-gallery.soracom.io (English): Ready-to-use IoT solution template setup guides.\n- iot-template-gallery.soracom.jp (Japanese): Ready-to-use IoT solution template setup guides.\n- iot-usecase.com (Japanese): IoT use cases showing SORACOM across industries.\n- soracom.io (English): Official blog: announcements, tutorials, event reports, and customer stories.\n- soracom.io/terms (English): Contract terms and conditions for SORACOM services in English, by region.\n- soracom.jp/iot-recipes (Japanese): Step-by-step IoT solution recipes with SORACOM.\n- soracom.jp/iot_basics (Japanese): Introductory IoT fundamentals and related technologies.\n- soracom.jp/partners (Japanese): SORACOM Partner Space and certified partner information.\n- soracom.jp/services (Japanese): SORACOM service overviews and pricing.\n- soracom.jp/store (Japanese): SORACOM IoT Store devices and starter kits.\n- soracom.jp/support_partners/certified_device (Japanese): SORACOM certified and compatible IoT device catalog.\n- soracom.jp/terms (Japanese): Contract terms and conditions (利用規約) for SORACOM services in Japanese.\n- support.soracom.io/hc/en-us (English): SORACOM support FAQs.\n- support.soracom.io/hc/ja (Japanese): SORACOM support FAQs.\n- users.soracom.io (Japanese): SORACOM User Site docs for service usage and configuration."
        }
      }
    }
    arguments 75 lines
  • search_api_docs reads unknown 4h ago

    Search SORACOM API documentation, CLI references, and SAM permissions. Use for exact API endpoints, soracom-cli commands, or SAM permission strings. Use search_soracom_docs for service guides, console how-tos, pricing, or IoT recipes. Use get_document on `#/schema/<Name>` links in results to read full API schema fields.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "tag": {
          "type": "string",
          "maxLength": 128,
          "description": "Optional OpenAPI tag such as 'Sim', 'DataEntry', 'Stats', or 'Query'. Exact, case-insensitive; discover valid tags from result api_tag fields."
        },
        "path": {
          "type": "string",
          "maxLength": 128,
          "description": "Optional API path fragment, matched as a case-insensitive substring excluding the version prefix — e.g. '/sims' or 'subscribers', not '/v1/sims'."
        },
        "query": {
          "type": "string",
          "maxLength": 1000,
          "description": "Natural-language query or API endpoint name. Optional when tag, method, or path is supplied; omit to browse filtered operations."
        },
        "method": {
          "type": "string",
          "maxLength": 128,
          "description": "Optional HTTP method to narrow results (e.g. 'GET', 'POST'). Exact, case-insensitive match."
        },
        "language": {
          "enum": [
            "Japanese",
            "English"
          ],
          "type": "string",
          "description": "Documentation language. Omit to auto-detect; set only to pin one language."
        },
        "max_results": {
          "type": "integer",
          "default": 16,
          "maximum": 32,
          "minimum": 1,
          "description": "Maximum results to return (1-32). Increase when exploring."
        },
        "search_mode": {
          "enum": [
            "hybrid",
            "keyword",
            "semantic"
          ],
          "type": "string",
          "default": "hybrid",
          "description": "Search strategy: 'hybrid' combines keyword and vector search; 'keyword' matches exact API paths, operationIds, and parameter names; 'semantic' uses vector similarity only."
        }
      }
    }
    arguments 50 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 5ee4b3c1f2167b03.

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

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.