Atlas entry
blip-board.app
5 capabilities over MCP. First atlas observation.
Surfaces
5 protocols checked
| ARD | Not found | No document retrieved |
|---|---|---|
| A2A | Not found | 0 skills |
| MCP | Valid | 2025-11-25 · 5 tools · 0 resources · 0 prompts |
| OpenAPI | Not detected | 0 operations |
| WebMCP | Not detected | 0 declarative form tools · experimental |
Exact states and meaning
- ARDabsent
Exact state: not found · No document retrieved
The supported discovery location returned no matching document.
Not found does not prove the service exposes no such interface elsewhere.
Not observed / not fetched
- A2Aabsent
Exact state: not found · 0 skills
The supported discovery location returned no matching document.
Not found does not prove the service exposes no such interface elsewhere.
Not observed / not fetched
- MCPobserved
Exact state: valid · Revision 2025-11-25 · 5 tools · 0 resources · 0 prompts
A usable protocol document was retrieved and validated.
Directly observed
- OpenAPIabsent
Exact state: not detected · 0 operations
No endpoint was established from the evidence and scope that InterfaceDelta inspected.
Not detected does not prove that no endpoint exists.
Not observed / not fetched
- WebMCPabsent
Exact state: not detected · 0 declarative form tools · experimental
No named declarative WebMCP form tools were observed in the origin root HTML.
Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.
Not observed / not fetched
Capabilities
5 · inventory complete
Summary of the AI readings · beta
The service lists 5 capabilities, and 4 have AI readings.
delete-board-tool is read as deleting or cancelling records.
update-board-tool is read as changing records.
create-board-tool is read as creating records.
Rows named: delete-board-tool · update-board-tool · create-board-tool
Written by code from the AI readings on this page: it groups them and says nothing they do not.
The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.
MCP tools 5
create-board-toolinputs
layoutId,name(required)AI Creates records 0.90
delete-board-toolinputs
boardUrl(required),pushToken(required)AI Deletes or cancels records 0.94
push-scenes-toolinputs
boardUrl(required),pushToken(required),replace,scenes(required) and 1 moreread-board-toolinputs
boardUrl(required)AI Reads only 0.90
update-board-toolinputs
boardUrl(required),name,pushToken(required),styleOverridesand 1 moreAI Changes records 0.90
Not observed in this Passport: A2A skills, MCP resources, MCP prompts, OpenAPI operations.
Declared and observed
No tools declare hints.
A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.
Atlas history
1 observation
- 5 capabilities · MCP 2025-11-25 · MCP endpoint validFirst observation
Fingerprint and versions
- Fingerprint
8e018e462b332e5f2536e59e76c266795af07a00278aac22c9a6ff687df2817a- Passport schema
- 0.5.0, passport-semantic-v4
- Consistency
- MCP_PROMPTS_ADVERTISEMENT_LIST: match · MCP_RESOURCES_ADVERTISEMENT_LIST: match · 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.
About this entry
app.blip-board/blipboardListedOfficial MCP Registry · first listed 14 Sep 2026 · last listed 27 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:a581bd6cc0f7aa26764a4e7700242e0271e6b248c26bdeb65ce19933e5ec0166- Locator SHA-256
5f5fbeb68d6c72e826dd43e06430e5300525dcb6a9dda8630226d2ef8dbd25b1- Snapshot generated
- 4 Nov 2026, 00:59 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.

