Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tribunal TRT1: Certidão Eletrônica de Ações Trabalhistas (CEAT)

REMOTE · API.MCP.AI · SCANNED AUG 22

Tribunal TRT1: Certificate Eletrônica de Ações Trabalhistas (CEAT), official-source lookup. Platform

Available components

remote · api.mcp.ai 46
46 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 124 tokens (~124/item across 0 items; 0 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 3 days we've observed: 7 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.mcp.ai

# add to Claude Code
claude mcp add --transport http mcp-dir-tribunal-trt1-ceat-mcp https://api.mcp.ai/p_tribunal_trt1_ceat
# ~/.codex/config.toml
[mcp_servers.mcp-dir-tribunal-trt1-ceat-mcp]
url = "https://api.mcp.ai/p_tribunal_trt1_ceat"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mcp-dir-tribunal-trt1-ceat-mcp": {
      "type": "remote",
      "url": "https://api.mcp.ai/p_tribunal_trt1_ceat",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mcp-dir-tribunal-trt1-ceat-mcp --url https://api.mcp.ai/p_tribunal_trt1_ceat --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  mcp-dir-tribunal-trt1-ceat-mcp:
    url: "https://api.mcp.ai/p_tribunal_trt1_ceat"
// mcp.json
{
  "mcpServers": {
    "mcp-dir-tribunal-trt1-ceat-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_tribunal_trt1_ceat"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Aug 26 +18
    • Stability: unverified → fail ▼ security
    • Schema quality: fail → unverified ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Schema quality: 144 → 124 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 21 Aug 26 −33
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.03 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 20 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.9.255 → 0.9.258 functional
  • 19 Aug 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Aug 2026 · Probed https://api.mcp.ai/p_tribunal_trt1_ceat

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ai CN=WE1,O=Google Trust Services,C=US 31 Jul 2026 29 Oct 2026 ECDSA 256 ECDSA-SHA256 796a3b1f576e3f2e133c5d19d8f7be3b
SANs: mcp.ai, *.mcp.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of api.mcp.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
mcp.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.mcp.ai/p_tribunal_trt1_ceat Verified 200
http (plaintext) http://api.mcp.ai/p_tribunal_trt1_ceat Inconclusive 406
MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

No tool schema has been captured from this endpoint yet.