Skip to main content
Glama
Sign In

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

by io.github.mcp-dir
OverviewDiscussionsAdmin

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
mcp-dir/tribunal_trt1_ceat-mcp
GitHub Stars
0
Server Listing
Tribunal TRT1: Certidão Eletrônica de Ações Trabalhistas (CEAT)
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation4/5

Most tools have clearly distinct roles: authenticate handles login, connect shows connection state, marketplace manages catalog operations, and the domain tool is unique. However, connect and toolkit_info both report connection status and could be confused. report_bug and show_version are trivial but distinct.

Naming Consistency2/5

Tool names mix styles: pure verbs (authenticate, connect), noun (marketplace), verb_noun (report_bug, show_version), and noun_noun (toolkit_info, tribunal_trt1_ceat_consultar). The domain tool follows a completely different convention from the platform tools, breaking consistency.

Tool Count3/5

Seven tools is within a reasonable size, but the server is named after a specific tribunal service while most tools are generic platform admin features. The count feels appropriate for a platform but mismatched for the stated domain. It borders on including too many unrelated tools.

Completeness2/5

The domain (CEAT) has only a single consultar tool, with no other operations like listing certificates, downloading, or managing requests. The platform tools cover the MCP lifecycle well but are unrelated to the domain. This leaves significant gaps for any real-world workflow.

Available Tools

7 tools
authenticateA
Idempotent
Inspect

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header Authorization: Bearer <token> for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "" } after the user pastes, or with no args to get the link.

Inputs: token.

connectA
Read-onlyIdempotent
Inspect

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Inputs: no named parameters.

marketplaceAInspect

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/ link that opens without login.

Inputs: limit, query, action, mcp_id, +19 more.

report_bugA
Idempotent
Inspect

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Inputs: message (required), context, conversation.

show_versionA
Read-onlyIdempotent
Inspect

Show the current MCP platform and adapter versions.

Inputs: no named parameters.

toolkit_infoA
Read-onlyIdempotent
Inspect

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Inputs: no named parameters.

tribunal_trt1_ceat_consultarA
Read-onlyIdempotent
Inspect

Tribunal TRT1: Certidão Eletrônica de Ações Trabalhistas (CEAT), consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).

Inputs: cpf, cnpj.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources