Is the Texs Tapercraft MCP server down?

mcp-registry/org.texs/tapercraft · v1.0.0

Also listed as mcp-registry/org.texs.vhs/tapercraft · primary listing: mcp-registry/org.texs.vhs/tapercraft

healthy
Last checked 2026-10-26 22:34 UTC · handshake 1.8s

As of 2026-10-26 22:34 UTC, the Texs Tapercraft MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,969
outages (90d)
0
tools
16

Compose printable VHS, DVD, cassette, CD and vinyl packaging from any movie, show, or album.

Point your MCP client at this streamable-http endpoint: https://vhs.texs.org/mcp

Agent-readiness: B (84/100)

B (84/100): 0 error(s), 3 warning(s) across 16 tool(s); ~7,908 tokens of tool definitions.
Scores higher than 42% of 15,781 MCP servers Glimind has audited.
Its tool list costs an agent ~7,908 tokens per session — more than 65% of servers.
83 → 84 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions68
Safety hints100
Token cost84
Client compatibility70
Protocol100
Reliability85
Stability68

What to fix (5)

2 tool definition(s) exceed ~1,200 tokens each (largest: save_design, ~2,803).

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,393 tokens every session. How to fix →

Tools: save_design, compose_design · saves ~4,393 tokens/session

7 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: compose_design, delete_design, get_content, get_export, save_design

Handshake + tools/list takes ~2,104 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.

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. How to fix →

In the last 30 days: 0 tool(s) removed and 8 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. How to fix →

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/org.texs/tapercraft"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/org.texs/tapercraft"}) 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%2Forg.texs%2Ftapercraft.svg)](https://glimind.com/server/mcp-registry%2Forg.texs%2Ftapercraft?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Forg.texs%2Ftapercraft?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.texs%2Ftapercraft.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.texs%2Ftapercraft.svg
   :target: https://glimind.com/server/mcp-registry%2Forg.texs%2Ftapercraft?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:2de5b5cfcbf331cf…, first seen 2026-10-17, included at leaf 3979 of 75,854. Version history · verify what your client received.

Tools (16)

Compare: most reliable design servers · most reliable media servers · most reliable files servers · most reliable knowledge servers · most reliable other 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 Texs Tapercraft MCP server down right now?

As of 2026-10-26 22:34 UTC, the Texs Tapercraft MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Texs Tapercraft MCP server provide?

Texs Tapercraft MCP server advertises 16 tools, including compose_design, delete_design, delete_upload, describe_format, export_design.

How do I install Texs Tapercraft MCP server?

Point your MCP client at this streamable-http endpoint: https://vhs.texs.org/mcp

Is the Texs Tapercraft MCP server safe to connect to an AI agent?

Glimind scanned all 16 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 Texs Tapercraft 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.

Feedback
Help us improve