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

install.md-anonymous

https://install.md

Registry code: f8e5611542bab454

api record

Create guides to instruct coding agents to use your software (SDK, library, framework, API, etc).

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

endpoint
https://install.md/mcp/try
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 install.md-anonymous live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is install.md-anonymous free to use?
Yes — the hub reached it with no key and no payment.
What tools does install.md-anonymous have?
13 tools: delete_data_source, get_project_details, delete_project, add_tool, toggle_tool, add_data_source, create_session, create_project, ….
Is install.md-anonymous 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
439ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 335 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • create an agent install guide project
  • add a data source to a project
  • add a step to a guide
  • reorder guide steps
takes → gives
text → data
tools
2 reads11 changes data
_ 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 13 tools
13 never probed 0 of 13 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.

  • delete_data_source changes data unknown never probed

    Delete a data source from a project

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "data_source_id"
      ],
      "properties": {
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        },
        "data_source_id": {
          "type": "string",
          "description": "The ID of the data source to delete"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_project_details reads unknown 16h ago

    Get detailed information about a specific project in the session

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "project_slug"
      ],
      "properties": {
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        },
        "project_slug": {
          "type": "string",
          "description": "The slug of the project to get details for"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • delete_project changes data unknown never probed

    Delete a project from the anonymous session

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "project_slug"
      ],
      "properties": {
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        },
        "project_slug": {
          "type": "string",
          "description": "The slug of the project to delete"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • add_tool changes data unknown never probed

    Add a new tool/step to a project

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "project_slug",
        "name",
        "display_name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The unique name of the tool (used as identifier)"
        },
        "tool_type": {
          "enum": [
            "step",
            "builtin",
            "tip"
          ],
          "type": "string",
          "default": "step",
          "description": "The type of tool (step, builtin, tip)"
        },
        "is_enabled": {
          "type": "boolean",
          "default": true,
          "description": "Whether the tool is enabled"
        },
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        },
        "step_order": {
          "type": "number",
          "description": "The order of this step in the project workflow"
        },
        "description": {
          "type": "string",
          "description": "Description of what the tool does"
        },
        "tool_schema": {
          "type": "string",
          "description": "JSON schema for tool parameters"
        },
        "display_name": {
          "type": "string",
          "description": "The human-readable display name of the tool"
        },
        "project_slug": {
          "type": "string",
          "description": "The slug of the project to add the tool to"
        },
        "response_template": {
          "type": "string",
          "description": "Markdown template for tool response"
        }
      },
      "additionalProperties": false
    }
    arguments 59 lines
  • toggle_tool changes data unknown never probed

    Toggle a tool's enabled/disabled state

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "tool_id"
      ],
      "properties": {
        "tool_id": {
          "type": "string",
          "description": "The ID of the tool to toggle"
        },
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • add_data_source changes data unknown never probed

    Add a new data source to a project

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "project_slug",
        "url",
        "type"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The URL of the data source"
        },
        "type": {
          "enum": [
            "web_crawl",
            "git_clone",
            "resource_load"
          ],
          "type": "string",
          "description": "The type of data source"
        },
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        },
        "project_slug": {
          "type": "string",
          "description": "The slug of the project to add the data source to"
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • create_session changes data unknown never probed

    Create a new anonymous session for managing projects

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • create_project changes data unknown never probed

    Create a new project in the anonymous session

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "name",
        "slug"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The display name of the project"
        },
        "slug": {
          "type": "string",
          "description": "The URL slug for the project (used in URLs)"
        },
        "is_public": {
          "type": "boolean",
          "default": false,
          "description": "Whether the project is public or private"
        },
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        },
        "overview_content": {
          "type": "string",
          "default": "",
          "description": "Markdown content for the project overview"
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • update_project changes data unknown never probed

    Update an existing project in the anonymous session

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "project_slug"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The display name of the project"
        },
        "slug": {
          "type": "string",
          "description": "The URL slug for the project (used in URLs)"
        },
        "is_public": {
          "type": "boolean",
          "description": "Whether the project is public or private"
        },
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        },
        "project_slug": {
          "type": "string",
          "description": "The slug of the project to update"
        },
        "overview_content": {
          "type": "string",
          "description": "Markdown content for the project overview"
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • update_tool changes data unknown never probed

    Update an existing tool

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "tool_id"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The unique name of the tool (used as identifier)"
        },
        "tool_id": {
          "type": "string",
          "description": "The ID of the tool to update"
        },
        "tool_type": {
          "enum": [
            "step",
            "builtin",
            "tip"
          ],
          "type": "string",
          "description": "The type of tool (step, builtin, tip)"
        },
        "is_enabled": {
          "type": "boolean",
          "description": "Whether the tool is enabled"
        },
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        },
        "step_order": {
          "type": "number",
          "description": "The order of this step in the project workflow"
        },
        "description": {
          "type": "string",
          "description": "Description of what the tool does"
        },
        "tool_schema": {
          "type": "string",
          "description": "JSON schema for tool parameters"
        },
        "display_name": {
          "type": "string",
          "description": "The human-readable display name of the tool"
        },
        "response_template": {
          "type": "string",
          "description": "Markdown template for tool response"
        }
      },
      "additionalProperties": false
    }
    arguments 55 lines
  • delete_tool changes data unknown never probed

    Delete a tool from a project

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "tool_id"
      ],
      "properties": {
        "tool_id": {
          "type": "string",
          "description": "The ID of the tool to delete"
        },
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • reorder_steps changes data unknown never probed

    Reorder tools/steps in a project

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id",
        "project_slug",
        "tool_orders"
      ],
      "properties": {
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        },
        "tool_orders": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "tool_id",
              "step_order"
            ],
            "properties": {
              "tool_id": {
                "type": "string",
                "description": "The ID of the tool to reorder"
              },
              "step_order": {
                "type": "number",
                "description": "The new step order for the tool"
              }
            }
          },
          "description": "Array of tool IDs and their new step orders"
        },
        "project_slug": {
          "type": "string",
          "description": "The slug of the project to reorder tools in"
        }
      },
      "additionalProperties": false
    }
    arguments 40 lines
  • list_projects reads unknown 16h ago

    List all projects in the anonymous session

    mcp-tool

    {
      "type": "object",
      "required": [
        "session_id"
      ],
      "properties": {
        "session_id": {
          "type": "string",
          "description": "The anonymous session ID"
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 f8e5611542bab454.

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