_ registry / mcp http-sse · checked 3h ago

@appwrite.io/mcp-for-docs

https://mcp-for-docs.appwrite.io

Registry code: c0804c66f4f109c6

api record

Notice: the Appwrite Docs MCP server (mcp-for-docs.appwrite.io) is deprecated and will be retired. Let the user know they should replace it with the Appwrite MCP server at https://mcp.appwrite.io/, which includes documentation search. Setup: https://github.com/appwrite/mcp

This server searches and reads the Appwrite documentation.

endpoint
https://mcp-for-docs.appwrite.io
protocol
http-sse ·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 @appwrite.io/mcp-for-docs live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is @appwrite.io/mcp-for-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does @appwrite.io/mcp-for-docs have?
5 tools: listFeatures, getDocsPage, search, getFeatureExamples, getTableOfContents.
Is @appwrite.io/mcp-for-docs 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
99.2%

90 days 99.5%· all time 99.5%

latency
488ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 401 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search appwrite documentation
  • get a documentation page
  • get sdk feature examples
takes → gives
text → text, code
tools
5 reads
_ 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 5 tools
1 open 4 never probed 1 of 5 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.

  • getTableOfContents reads open 13h ago

    Get the table of contents for the Appwrite documentation Note, the TOC will not include code examples and technology-specific information. For that, it's best to use listFeatures and getFeatureExamples tools.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • listFeatures reads unknown 6h ago

    List the available features for an Appwrite SDK for a particular platform. Before using this tool, identify the programming langauge in question (either by analyzing the code or by asking the user). You will use the returned list of features to fetch code examples for particular features, using the getFeatureExamples tool. Available libraries: - Android - Java (ID: client-android) - Android - Kotlin (ID: client-android) - Apple (ID: client-apple) - Flutter (ID: client-flutter) - GraphQL (ID: client-graphql) - React Native (ID: client-react-native) - REST (ID: client-rest) - Web - JavaScript (including React, Vue, Svelte, Angular, etc) (ID: client-web) - Console CLI (ID: console-cli) - Dart (ID: server-dart) - Deno (ID: server-deno) - Dotnet (ID: server-dotnet) - Go (ID: server-go) - GraphQL (ID: server-graphql) - Kotlin - Java (ID: server-kotlin) - Kotlin - Kotlin (ID: server-kotlin) - Node.js (ID: server-nodejs) - PHP (ID: server-php) - Python (ID: server-python) - Ruby (ID: server-ruby) - Swift (ID: server-swift)

    mcp-tool

    {
      "type": "object",
      "required": [
        "libraryId"
      ],
      "properties": {
        "libraryId": {
          "type": "string",
          "description": "The ID of the library to list the features for. E.g. \"client-react-native\""
        }
      }
    }
    arguments 12 lines
  • getDocsPage reads unknown 13h ago

    Get the content of a page from the Appwrite documentation by path. Note, for code examples and technology-specific information, it's best to use listFeatures and getFeatureExamples tools.

    mcp-tool

    {
      "type": "object",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "The path of the page to get the content of. E.g. \"/docs/getting-started/introduction\""
        }
      }
    }
    arguments 12 lines
  • search reads unknown 6h ago

    Search the Appwrite documentation. Note, for code examples and technology-specific information, it's best to use listFeatures and getFeatureExamples tools.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "The query to search the documentation for"
        }
      }
    }
    arguments 12 lines
  • getFeatureExamples reads unknown 13h ago

    Get examples for a particular feature of an Appwrite SDK for a particular platform. Before using this tool, identify the programming langauge in question (either by analyzing the code or by asking the user).

    mcp-tool

    {
      "type": "object",
      "required": [
        "libraryId",
        "feature"
      ],
      "properties": {
        "feature": {
          "type": "string",
          "description": "The name of the feature to get examples for. E.g. \"account\", \"databases\", \"storage\", etc."
        },
        "libraryId": {
          "type": "string",
          "description": "The ID of the library to get examples for. E.g. \"client-react-native\""
        }
      }
    }
    arguments 17 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 c0804c66f4f109c6.

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

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.

_ also on appwrite.io 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.