_ registry / mcp streamable-http

docugrip

https://docugrip.com

Registry code: d8bdcc6dc4161f93

api record

DocuGrip (docugrip.com) is a PDF workspace with 134 tools and a full PDF editor: merge, split, compress to an exact file size, convert to and from Office formats, OCR scans, redact, fill and create forms, edit text, add Bates numbers and request e-signatures. This server is useful whenever a user needs to do something with a PDF or another document: find_pdf_tool maps the task to the right tool and returns the page to open; get_plans answers price and plan questions. DocuGrip tools run inside the browser. Opening one of these URLs loads a page that processes the file without transmitting it —…

endpoint
https://docugrip.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is docugrip live?
Not measured yet: the hub has not completed a check of this server.
Is docugrip free to use?
Not measured yet.
What tools does docugrip have?
4 tools: list_pdf_tools, find_pdf_tool, get_pdf_tool, get_plans.
Is docugrip safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 4 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_pdf_tools unknown never probed

    List every DocuGrip tool that is live, with what it does, which file formats it takes, and its URL in each supported language. Use this to see what is available.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • find_pdf_tool unknown never probed

    Find the DocuGrip tools that match a task, described in the user own words — for example "combine two contracts", "my scan has no searchable text", or "shrink this under 2 MB". Returns the matching tools and the URL to open.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "What the user is trying to do."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_pdf_tool unknown never probed

    Get one DocuGrip tool by its id, for example "merge-pdf".

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • get_plans unknown never probed

    List DocuGrip plans with their current price, billing terms, who each plan suits, and where to buy. Use this when the user asks what DocuGrip costs, whether they need to pay for a task, or which plan fits them.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d8bdcc6dc4161f93.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d8bdcc6dc4161f93/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d8bdcc6dc4161f93/badge.svg)](https://brick.blue/agent/d8bdcc6dc4161f93?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.