_ registry / mcp http-sse · checked just now

certscore

https://mcp.certscore.ai

Registry code: 53f2eaf0241abd96

api record

{"setup":{"route":"light","scopesGranted":null,"createAllowedByScope":null,"resources":["certscore://project-instructions","certscore://example-report"],"prompts":["certscore_launch_review","certscore_compare_scans","certscore_remediation_checklist"],"quotaRemaining":null,"quotaNote":"Remaining allowance is not loaded at handshake. Scan creation enforces current workspace and requester limits; inspect quota errors rather than assuming a fresh…

endpoint
https://mcp.certscore.ai/mcp/light
protocol
http-sse ·2025-06-18
authentication
bearer
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 certscore live?
Yes — it answered the hub's last check (checked just now). It answered 100% of checks over the last 30 days.
Is certscore free to use?
Yes — the hub reached it with no key and no payment.
What tools does certscore have?
4 tools: certscore_get_scan_bundle, certscore_get_scan_status, certscore_get_report_evidence_page, certscore_scan_site.
Is certscore 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
live
uptime, 30 days
100%

90 days 99.1%· all time 99.2%

latency
590ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 467 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • scan a website for privacy issues
  • inventory cookies and trackers
  • get scan findings and evidence
takes → gives
text → data
tools
3 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ 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.

  • certscore_get_scan_bundle reads unknown 13h ago

    Main answer for a completed or completed-limited scan: canonical findings, next steps, supporting evidence, score, date/region, coverage and report URL. An existing scanId is enough; no new scan is created. The evidence index describes response delivery, never evidence absence. Optional next actions lead to deeper report tables, tracking workpapers and JSON/CSV exports. Use detail=evidence for request examples and policy candidates, including scans with no findings; detail=full adds bounded retained context. Preserve returned/total counts and omission metadata. Accept/Reject execution succeeded means a completed click and bounded observation; succeeded_with_confirmation additionally verifies the consent decision. Retained after-click facts remain distinct from registered decisions. Absent or failed capture remains explicitly limited. Use canonical findings for scoring effects. A later missing finding does not prove a fix. Results are automated public-web observations, not legal advice, certification, or a compliance determination.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "scanId"
      ],
      "properties": {
        "detail": {
          "enum": [
            "summary",
            "findings",
            "evidence",
            "full"
          ],
          "type": "string",
          "description": "Response detail. Defaults to summary; evidence and full opt into heavier retained context."
        },
        "scanId": {
          "type": "string",
          "minLength": 1,
          "description": "Stable CertScore scan ID."
        },
        "maxBytes": {
          "type": "integer",
          "maximum": 200000,
          "minimum": 5000,
          "description": "Requested serialized structured response budget in bytes. The full profile defaults to 50000. MCP Light defaults to and applies a transport-safe 25000-byte ceiling; larger Light requests are clamped and reported in response metadata."
        },
        "maxFindings": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum compact findings to return. Defaults to 5 for summary and 20 otherwise."
        },
        "maxPreConsentRows": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum compact pre-consent inventory rows to return. Defaults to 20."
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • certscore_get_scan_status reads unknown 13h ago

    Returns lifecycle status for a stable CertScore scanId. Active responses include phase, heartbeat, estimated progress, retryAfterSeconds, and sometimes a bounded preliminary preConsentPreview. Terminal responses include completion status, CertScore score and risk metadata when available, coverage, persisted execution region and timestamps, report URL, and a next-action field. Preliminary observations are distinct from completed findings.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "scanId"
      ],
      "properties": {
        "scanId": {
          "type": "string",
          "minLength": 1,
          "description": "Stable CertScore scan ID returned by certscore_scan_site."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • certscore_get_report_evidence_page reads unknown 13h ago

    For a focused question, use section=cmp, cms, consent, gpc, policy, tracking, transport, forms or accessibility. This returns selected retained report sections plus shared scan, score, findings and coverage context. CMP includes all 13 criteria with their assessment results and retained comparisons; CMS includes platform/version evidence and existing advisories. Policy also includes retained privacy-choice controls, unverified link candidates and notice passages; California-focused reports include their shared privacy section. detailedEvidence carries shared display wording, counts and cross-links; these audit rows are not additional findings. Use reviewFocus=gdpr_eprivacy or ccpa_cpra to match the corresponding web/PDF/Word view; omit it to retain the scan default. Preserve reviewFocus and section on cursor continuation; unselected or not-returned fields are not evidence of absence. Use workpaper=tracking separately for the starting-page tracking inventory, privacy choices/notices and GPC evidence, with JSON and CSV downloads. Never combine section and workpaper. The workpaper selector also applies to every continuation request. Otherwise retrieve scan report display content as paginated JSON, without internal diagnostic JSON downloads. The response also offers a single-file full JSON download; private JSON download links expire after five minutes and need no OAuth header; use pagination if your host blocks file downloads. Repeated display records use reportContentRef JSON Pointers. Includes evidence tables, full-site page and resource inventories, all retained additional-page form fields, form snapshot download references, and retained limitations. Snapshot images are downloaded separately from the returned URLs, with OAuth bearer authentication for workspace scans. Available on OAuth and Light. Start with scanId; follow pagination.nextCursor until complete. Pages share a snapshot; restart if it changes. Each entry has a JSON Pointer path and value; oversized strings use numbered parts. Export completion is not complete observation coverage. Use the concise scan bundle for summaries; use this tool for exhaustive report evidence. No new scan is created.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "scanId"
      ],
      "properties": {
        "cursor": {
          "type": "string",
          "maxLength": 100
        },
        "scanId": {
          "type": "string",
          "format": "uuid"
        },
        "section": {
          "enum": [
            "consent",
            "gpc",
            "policy",
            "tracking",
            "transport",
            "forms",
            "accessibility",
            "cmp",
            "cms"
          ],
          "type": "string"
        },
        "workpaper": {
          "type": "string",
          "const": "tracking"
        },
        "reviewFocus": {
          "enum": [
            "gdpr_eprivacy",
            "ccpa_cpra"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • certscore_scan_site changes data unknown never probed

    Use for a user-requested website launch review, vendor assessment, cookie/tracker inventory, consent/GPC investigation or privacy-policy review. A public URL or domain is enough. Creates a privacy scan or reuses an eligible recent completed scan; default freshness=latest saves new-scan quota. Use refresh only for an explicitly requested fresh scan or post-fix recheck. Retain scanId, poll certscore_get_scan_status only while active at retryAfterSeconds, then read certscore_get_scan_bundle. A preliminary preConsentPreview is not final findings or totals. Coverage includes pre-consent storage, trackers, consent and CMP signals, privacy-policy disclosures, transport security and GDPR/ePrivacy or CCPA/CPRA review signals. Results are automated observations, not legal advice, certification, or a compliance determination. https://certscore.ai/developers/mcp.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "minLength": 1,
          "description": "Public URL or domain to scan."
        },
        "scanFrom": {
          "enum": [
            "eu_de",
            "eu_ie",
            "california"
          ],
          "type": "string",
          "description": "Optional execution region for a newly queued scan: eu_de, eu_ie, california, or the service default when omitted."
        },
        "freshness": {
          "enum": [
            "latest",
            "refresh"
          ],
          "type": "string",
          "description": "Scan freshness policy. latest allows eligible recent completed-result reuse when available; refresh requests a new scan. Defaults to latest."
        },
        "taskContext": {
          "type": "object",
          "properties": {
            "purpose": {
              "enum": [
                "prelaunch_review",
                "vendor_review",
                "tracking_check",
                "consent_gpc_check",
                "policy_review",
                "recheck",
                "other",
                "unknown"
              ],
              "type": "string"
            },
            "skillVersion": {
              "$ref": "#/properties/taskContext/properties/integrationId"
            },
            "integrationId": {
              "type": "string",
              "pattern": "^[a-zA-Z0-9][a-zA-Z0-9._-]*$",
              "maxLength": 80
            },
            "questionSource": {
              "enum": [
                "user_wording",
                "agent_paraphrase"
              ],
              "type": "string"
            },
            "questionSummary": {
              "type": "string",
              "maxLength": 8192,
              "minLength": 1
            },
            "integrationVersion": {
              "$ref": "#/properties/taskContext/properties/integrationId"
            },
            "shareForImprovement": {
              "type": "boolean"
            }
          },
          "description": "Optional caller-declared purpose and integration ID/version for usage research. Only include questionSummary when the user knowingly agrees to share a brief non-sensitive question for product improvement; label user_wording or agent_paraphrase. Never include chat history, personal/account details, secrets or URLs. Omission does not affect scanning.",
          "additionalProperties": false
        }
      },
      "additionalProperties": false
    }
    arguments 78 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 53f2eaf0241abd96.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/53f2eaf0241abd96/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/53f2eaf0241abd96/badge.svg)](https://brick.blue/agent/53f2eaf0241abd96?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.