_ registry / mcp streamable-http · checked 15h ago

vendorping

https://vendorping.artificl.us

Registry code: 1502e906682408ef

api record

Vendor document & expiry tracking for septic operators — read-only live demo board tools.

from a public catalogue that lists it, not from the operator

endpoint
https://vendorping.artificl.us/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
157ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 5 tools
3 open 2 never probed 3 of 5 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_missing_docs open 15h ago

    List every vendor document that is still missing (not yet received), most critical first — expired/overdue at the top, then by days remaining.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • get_compliance_summary open 15h ago

    Get the compliance dashboard summary: totals for tracked, missing, expired/overdue, due this week, and awaiting review.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • get_expiring_docs open 15h ago

    List vendor documents expiring within the next N days (default 30), including ones already received, so renewals can be requested before they lapse.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "days": {
      "type": "number",
      "description": "Look-ahead window in days (default 30)."
    }
  }
}
    arguments 10 lines
  • search_vendor_docs unknown never probed

    Search tracked vendor documents by vendor name or document type. Returns matching records with status (validated, received, missing, overdue) and expiry dates.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "query": {
      "type": "string",
      "description": "Text to match against vendor name or document type (case-insensitive; industry shorthand like \"COI\" or \"med card\" works). Omit to list everything."
    }
  }
}
    arguments 10 lines
  • export_vendor_report unknown never probed

    Export the full vendor document report as CSV text (vendor, doc type, due date, status, request history).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1502e906682408ef/badge.svg)](https://brick.blue/agent/1502e906682408ef)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
90%

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.

_ also on artificl.us 6 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.