Is the Homespun MCP server down?

mcp-registry/dev.homespun/homespun · v1.6.98

Also listed as awesome/homespunapps/homespun, glama/homespunapps/homespun

healthy
Last checked 2026-10-18 03:00 UTC · handshake 487ms

As of 2026-10-18 03:00 UTC, the Homespun MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
100%
checks observed
3,612
outages (90d)
9
tools
27

Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.

Install Homespun MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http homespun-mcp-server https://homespun.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "homespun-mcp-server": {
      "type": "http",
      "url": "https://homespun.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 4 warning(s) across 27 tool(s); ~17,730 tokens of tool definitions.
Scores higher than 52% of 15,350 MCP servers Glimind has audited.
Its tool list costs an agent ~17,730 tokens per session — more than 95% of servers.
85 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost44
Client compatibility70
Protocol100
Reliability85
Stability86

What to fix (5)

3 tool definition(s) exceed ~1,200 tokens each (largest: community, ~3,200).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~4,933 tokens every session.

Tools: community, deploy_app, attachments · saves ~4,933 tokens/session

Loading this server's tool list costs an agent ~17,730 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request.

Handshake + tools/list takes ~2,120 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 1 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.homespun/homespun"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.homespun/homespun"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.homespun%2Fhomespun.svg)](https://glimind.com/server/mcp-registry%2Fdev.homespun%2Fhomespun?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.homespun%2Fhomespun?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.homespun%2Fhomespun.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.homespun%2Fhomespun.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.homespun%2Fhomespun?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:623bfdb60e10b8e0…, first seen 2026-10-17, included at leaf 3838 of 19,919. Version history · verify what your client received.

Tools (27)

Compare: most reliable data servers · most reliable other servers · most reliable devops servers · most reliable files servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Homespun MCP server down right now?

As of 2026-10-18 03:00 UTC, the Homespun MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Homespun MCP server provide?

Homespun MCP server advertises 27 tools, including add_row, agent, apps, attachments, community.

How do I install Homespun MCP server?

Point your MCP client at this streamable-http endpoint: https://homespun.dev/mcp

Is the Homespun MCP server safe to connect to an AI agent?

Glimind scanned all 27 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Homespun MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.