Atlas entry
api. pressa. dev
No capabilities retained; MCP observed, and the MCP endpoint was protocol error. First atlas observation.
Atlas history
1 observation
- 0 capabilities · MCP · MCP endpoint protocol errorFirst observation
Fingerprint and versions
- Fingerprint
bb667158c39d6dda4f15ead8e67ad1b093fe6fe09de80d62c707eaf04ad4a707- Passport schema
- 0.5.0, passport-semantic-v4
- Consistency
- 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
io.github.pressa-dev/pressaListedOfficial MCP Registry · first listed 9 Nov 2026 · last listed 9 Nov 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:63964a5814880f20aebc68003f7602e576a265df8a2da0e1955fe11834fe2583- Locator SHA-256
55bfbcee9e1206eac2ef437afe98d4fc7d288ac38f8c487fb5a794dc9fb99782- Snapshot generated
- 12 Nov 2026, 05:45 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.

