mcp-registry/com.preteworks/preteworks-api · v1.1.0
Verdict. Preteworks Api MCP server answered 99.91% of Glimind's liveness checks over 30 days, better than 31% of MCP servers, with 2057 ms median handshake and 4 outages in 90 days. Its agent-readiness grade is A (92/100) across 29 tools, costing an agent about 4,222 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.91% | 31% of MCP servers |
| Median handshake latency | 2057 ms | 5% of MCP servers |
| p95 handshake latency | 4272 ms | — |
| Checks in 30 days | 4,934 | — |
| Outages, 90 days | 4 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 92/100 (A) | 73% of MCP servers |
| Tools | 29 | — |
| Tool-list size for an agent | ~4,222 tokens | 40% of MCP servers |
| Days observed | 29 | — |
As of 2026-10-26 19:39 UTC, the Preteworks Api MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 2 minutes.
One key for the document-to-web pipeline: scrape, AI-extract, build & edit PDFs, fill forms.
Claude Code
claude mcp add --transport http preteworks-api-mcp-server https://api.preteworks.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"preteworks-api-mcp-server": {
"type": "http",
"url": "https://api.preteworks.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 parameter(s) across 1 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 →
Handshake + tools/list takes ~2,049 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 →
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/com.preteworks/preteworks-api"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.preteworks/preteworks-api"}) over MCP.
render_document ~259 tokensextract_data ~234 tokensanswer_from_document ~225 tokenssummarize_document ~224 tokensnumber_pdf ~197 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fcom.preteworks%2Fpreteworks-api?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.preteworks%2Fpreteworks-api?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.preteworks%2Fpreteworks-api.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.preteworks%2Fpreteworks-api.svg :target: https://glimind.com/server/mcp-registry%2Fcom.preteworks%2Fpreteworks-api?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:367932f53e37d70b…, first seen 2026-10-17, included at leaf 14921 of 75,084. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable web servers · most reliable files servers · most reliable productivity servers
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.
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"
}
}
}
As of 2026-10-26 19:39 UTC, the Preteworks Api MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 2 minutes.
Preteworks Api MCP server advertises 29 tools, including answer_from_document, batch_scrape, crawl_site, data_to_spreadsheet, docx_to_pdf.
Point your MCP client at this streamable-http endpoint: https://api.preteworks.com/mcp
Glimind scanned all 29 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.
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.