Is the Dirtsmith outside-tools rate sheet MCP server down?

mcp-registry/dev.workers.bfurrow26.dirtsmith-go/rate-sheet · registry v2026.1016.1147 · server reports v2026-10-17.1

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 17:00 UTC · handshake 408ms

As of 2026-11-22 17:00 UTC, the Dirtsmith outside-tools rate sheet 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
888
outages (90d)
0
tools
15

Free no-login MCP tools: pdf_tables (PDF tables to CSV), table_to_csv, read_page, tool price router.

Point your MCP client at this streamable-http endpoint: https://dirtsmith-go.bfurrow26.workers.dev/mcp?ref=mcpreg

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 3 warning(s) across 15 tool(s); ~1,839 tokens of tool definitions.
Scores higher than 20% of 27,660 MCP servers Glimind has audited.
Its tool list costs an agent ~1,839 tokens per session — more than 50% of servers.
78 → 78 since 2026-11-16
no tool-poisoning patterns
Descriptions34
Safety hints51
Schemas87
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility100

What to fix (4)

28 parameter(s) across 12 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: check_credit, claim_job, cost_estimate, fedreg_search, json_validate and 7 more

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: json_validate

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: submit_job

5 of 15 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_credit, claim_job, get_quote, list_jobs, submit_job

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 12 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.workers.bfurrow26.dirtsmith-go%2Frate-sheet/fixes

check_credit 1 change
{
  "name": "check_credit",
  "description": "Contractors/buyers: how many calls are left on a credit pass.",
  "inputSchema": {
    "type": "object",
    "required": [
      "credit"
    ],
    "properties": {
      "credit": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_quote 1 change
{
  "name": "get_quote",
  "description": "Buyers: price and how to pay for one tool. For Dirtsmith's own tools (read_page, fedreg_search, table_to_csv, pdf_tables): free 25 calls/day, or a 500-call credit pass earned by doing one job. Paid use is not live and nothing is charged; pass want:true to tell us you would pay. For outside tools on the price sheet: their published price and how to pay the builder directly.",
  "inputSchema": {
    "type": "object",
    "required": [
      "tool"
    ],
    "properties": {
      "tool": {
        "type": "string",
        "description": "Exact tool name, e.g. pdf_tables or Exa"
      },
      "want": {
        "type": "boolean",
        "description": "true = you would pay for this when paid use is live (counted, no charge)"
      },
      "calls": {
        "type": "integer",
        "description": "How many calls you expect (optional)"
      },
      "max_usd_per_call": {
        "type": "number",
        "description": "Optional: the most you would pay per call"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
json_validate 1 change
{
  "name": "json_validate",
  "description": "Dirtsmith-built free utility: validate JSON data against a JSON Schema subset; returns errors with paths.",
  "inputSchema": {
    "type": "object",
    "required": [
      "data",
      "schema"
    ],
    "properties": {
      "data": {
        "type": "string"
      },
      "schema": {
        "type": "object"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false
  }
}

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.workers.bfurrow26.dirtsmith-go/rate-sheet"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.workers.bfurrow26.dirtsmith-go/rate-sheet"}) 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fdev.workers.bfurrow26.dirtsmith-go%2Frate-sheet.svg)](https://glimind.com/server/mcp-registry%2Fdev.workers.bfurrow26.dirtsmith-go%2Frate-sheet?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.workers.bfurrow26.dirtsmith-go%2Frate-sheet?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fdev.workers.bfurrow26.dirtsmith-go%2Frate-sheet.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c1d2a3bfdfd71523…, first seen 2026-11-16, included at leaf 292371 of 384,671. Version history · verify what your client received.

Tools (15)

Compare: most reliable other servers · most reliable search servers · most reliable code servers · most reliable data servers · most reliable web 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?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Dirtsmith outside-tools rate sheet MCP server down right now?

As of 2026-11-22 17:00 UTC, the Dirtsmith outside-tools rate sheet 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 Dirtsmith outside-tools rate sheet MCP server provide?

Dirtsmith outside-tools rate sheet MCP server advertises 15 tools, including check_credit, claim_job, cost_estimate, fedreg_search, find_tool.

How do I install Dirtsmith outside-tools rate sheet MCP server?

Point your MCP client at this streamable-http endpoint: https://dirtsmith-go.bfurrow26.workers.dev/mcp?ref=mcpreg

Is the Dirtsmith outside-tools rate sheet MCP server safe to connect to an AI agent?

Glimind scanned all 15 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 Dirtsmith outside-tools rate sheet 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