Atlas entry

`rendafixa.api.br`

2 capabilities over MCP 2025-11-25. First atlas observation.

Observed 11 Nov 2026, 10:05 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 11 Nov 2026, 10:05 UTC
Signed: 11 Nov 2026, 10:30 UTC

Protocols: MCP
Tools: 2
Declared sign-in: None declared

Effects counted AI readings, beta

Moves money: 0
Deletes or cancels records: 0
Sends messages to people: 0
Changes permissions: 0
Runs code: 0
Asks a person: 0

2 tools examined; 2 counted above a measured threshold.

Declared vs read disagreements

Declared read-only, read as writing: 0
Declared destructive, read as not writing: 0
Declared non-destructive, read as deleting: 0
Declared closed-world, read as reaching out: 0

Change since previous: First observation
Label status: Current

Atlas history

1 observation

11 Nov 2026, 10:05 UTC2 capabilities · MCP 2025-11-25 · MCP endpoint validFirst observation
Fingerprint and versions
Fingerprint
44e7a8601f887b7fa269dacdcbf0595e7aa87446d3783527508382b8918085a8
Passport schema
0.5.0, passport-semantic-v4
Consistency
MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable

Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.

Declared and observed

Tool declarations are unavailable for this entry.

A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.

About this entry

br.api.rendafixa/renda-fixa
Listed
Official MCP Registry · first listed 30 Oct 2026 · last listed 30 Oct 2026

Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal

Identity and snapshot

Target key: sha256:fabf20ce6a00db84c9576b41bc9f2ef93f73228d5d1643f1d181fbfd13311e42
Locator SHA-256: 3c8cb9b81682f5ce6d2f60bbe6c3eed8c6b891e3789aafdbbc4a7480f7e65410
Snapshot generated: 11 Nov 2026, 22:36 UTC

The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.