
MeshVault Connectors
io.github.thefiredev-cloudv0.1.0Updated Oct 6, 2026
Read-only tools: EMS protocols, courts and judges, NPI and FDA data, GPU fit for open models.
Overview
A remote MCP server giving assistants read-only lookups for EMS protocols, judges and courts, US health data, and open-model GPU fit.
- What it does
- MeshVault Connectors exposes four read-only tool groups over Streamable HTTP. The ems group searches and retrieves EMS protocols and lists agencies and coverage; the legal group searches judges, courts and recent cases; the health group looks up NPI records and FDA drug labels, recalls and adverse events; the models group checks whether open models fit given hardware, estimates VRAM, lists GGUF files, searches Hugging Face and reads a GPU catalog. Every tool is annotated read-only and responses repeat that results are reference material, not medical or legal advice.
- When to use it
- Useful when an assistant needs quick reference lookups from public sources: EMS protocol text, judge and court background, US provider and drug data, or sizing an open model against available GPU memory. It is a lookup service rather than a system of record, so it suits research and drafting, not clinical or legal decisions.
- Requirements
- A remote endpoint at thefiredev.com; no local runtime or package install. Authentication is a bearer API key in the Authorization header, or OAuth for clients that prompt at connect time. A free key allows 100 calls per UTC day; the anonymous try endpoint allows 10 calls per day per network without credentials. Pro is $19 per month for 5,000 calls per day.
Installation
In SourceWeft
- Open MeshVault Connectors in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"meshvault-connectors": {
"type": "http",
"url": "https://thefiredev.com/mcp"
}
}
}README
MeshVault Connectors
Remote MCP server that gives ChatGPT, Claude and Gemini read-only tools in four groups. One deployable service (Vercel Function + static site), Streamable HTTP, OAuth 2.1 or API key, free tier, Pro plan through Stripe.
Every tool is annotated read-only. EMS results are education and reference, not medical direction; health data is not medical advice; legal data is not legal advice. Each response repeats the notice.
Use it
Server URL: https://thefiredev.com/mcp (landing page, docs and pricing: https://thefiredev.com/connectors)
Claude and ChatGPT custom connectors use OAuth: add the URL, and the sign-in page asks for a key or creates a free one. /mcp/try needs no credentials and allows 10 calls a day per network. Gemini CLI: gemini extensions install https://github.com/thefiredev-cloud/meshvault-connectors (set MESHVAULT_API_KEY).
Plans
Only tools/call counts. Calls rejected for bad input or failed by an upstream outage are refunded.
Architecture
State lives in one private Vercel Blob store (keys/, usage/, customers/, events/, oauth/). Writes use ETag compare-and-swap, so concurrent calls cannot overspend a quota.
OAuth refresh tokens are claimed by a compare-and-swap update. A reused token, including a losing concurrent refresh request, revokes the family. Access tokens check that family on each request, so revocation does not wait for the token's one-hour expiry.
Billing behaviour
- Checkout with an existing key upgrades that key. Cancellation downgrades it to Free.
- Checkout without a key issues a new Pro key, shown once on the confirmation page (sealed with AES-256-GCM for 24 hours). Cancellation revokes it.
- Fulfillment runs from both the webhook and the confirmation page. Both check Stripe's current subscription status, customer and configured Pro price before granting access; late event snapshots and reused success links cannot restore a canceled subscription.
- Webhook events handled:
checkout.session.completed,checkout.session.async_payment_succeeded,customer.subscription.updated,customer.subscription.deleted.
Develop
Environment variables are listed in .env.example. Use Stripe test-mode keys until you intentionally go live; stripe listen --forward-to localhost:8787/api/stripe/webhook gives a local webhook secret.
Deploy
Two supported shapes:
Own Vercel project. Import this repo (framework: Other; settings are in vercel.json), add a private Blob store, set the variables from .env.example, add the webhook endpoint https://<host>/api/stripe/webhook for the four events above.
Mounted in another site (how thefiredev.com runs it). node scripts/export-mount.mjs --out <host repo> --prefix /connectors writes one bundled Vercel Function (api/connectors.js) and the static pages under public/connectors/; --rewrites <file> also writes the vercel.json rewrites the host must contain. The host sets CONNECTORS_* variables (CONNECTORS_APP_SECRET, CONNECTORS_PUBLIC_BASE_URL, CONNECTORS_LANDING_PATH, CONNECTORS_STRIPE_SECRET_KEY, CONNECTORS_STRIPE_PRICE_PRO, CONNECTORS_STRIPE_WEBHOOK_SECRET) and a Blob store connected with variable prefix CONNECTORS_BLOB. The service owns /mcp, /oauth/*, /.well-known/oauth-*, /billing/*, /api/keys, /api/usage, /api/checkout, /api/billing, /api/stripe, /health.
Then publish server.json with mcp-publisher.
License
MIT. Data from third-party sources keeps its own terms; see each source.
Source: README.md at commit aeb37a7
Tools
0Version history
1- v0.1.0LatestOct 6, 2026
