Method · The observatory read back

The observatory reads itself being read.

Every tool invocation against the public MCP server writes one row to an append-only log. No raw IPs; session identifiers are salt-hashed in rows written from 2026-09-26; earlier rows hold them as received. These are the aggregates.

The reading

30-day window

Invocations	71,443
Succeeded	69,700
Errored	1,743
Distinct sessions	299
Distinct tools called	55
Agent families	7

What agents asked for

20 tools

Tool	Calls	Success	Median
`semantic_search`	436	38.3%	1174 ms
`list_watch_items`	319	85.9%	0 ms
`describe_corridor`	318	47.2%	0 ms
`describe_place`	317	69.4%	0 ms
`list_entities`	317	87.1%	0 ms
`describe_meeting`	311	83%	0 ms
`list_meetings`	282	89.4%	0 ms
`describe_zoning_signal`	280	100%	0 ms
`meeting_index`	221	86.4%	0 ms
`list_places`	218	100%	0 ms
`describe_entity`	210	54.3%	0 ms
`describe_watch`	208	53.8%	0 ms
`describe_pattern`	202	43.6%	0 ms
`list_patterns`	180	100%	0 ms
`get_track_record`	174	100%	0 ms
`list_corridors`	164	100%	0 ms
`trace_connection`	99	100%	0 ms
`__mcpcheckup_probe_nonexistent_tool__`	30	0%	0 ms
`sandbox.execute_shell`	9	0%	0 ms
`submit_agent_feedback`	5	100%	796 ms

Who was reading

Derived from user agent; unattributed traffic stays unattributed

Agent family	Calls	Sessions	Success
unknown	70,989	298	97.8%
curl	199	1	68.3%
browser	185	0	47%
anthropic-sdk	62	0	100%
claude	6	0	100%
gemini	1	0	0%
perplexity	1	0	0%

Which corner of the field

Records agents asked about by name

Record	Asked via	Calls
`us-27-south-lake`	`describe_corridor`	149
`winter-garden-pz-2026-10-agenda`	`describe_corridor`	118
`Clermont`	`meeting_index`	107
`clermont-florida`	`describe_place`	82
`minneola-florida`	`describe_place`	47
`us-27-south-lake`	`get_track_record`	42
`winter-garden-pz-2026-10-agenda`	`describe_meeting`	40
`winter-garden-pz-2026-10-agenda`	`describe_pattern`	40
`winter-garden-pz-2026-10-agenda`	`describe_place`	40
`winter-garden-pz-2026-10-agenda`	`describe_entity`	40
`winter-garden-pz-2026-10-agenda`	`describe_watch`	39
`leesburg-florida`	`list_watch_items`	39
`leesburg-florida`	`describe_place`	37
`Minneola`	`meeting_index`	36
`leesburg-florida`	`list_entities`	36

What agents told us

5 submissions via submit_agent_feedback

Category	Submitted	Reviewed
gap	2	0
suggestion	2	0
citation_request	1	0

How this is counted

One row per tool invocation against the public MCP server: timestamp, transport, tool name, sanitized arguments, result status, duration, and a derived agent family. Raw IP addresses are never stored; session identifiers are salt-hashed in rows written from 2026-09-26; earlier rows hold them as received. Aggregation runs through fixed database functions that return only grouped counts, so no individual call is retrievable from this page.

Agent family is inferred from the user agent, and traffic that does not identify itself is reported as unknown rather than attributed by guess, which is why unknown is the largest row above and should be read as a limit of the measurement, not a finding.