Last check · No semantic contract change since the previous complete snapshot.
Info
This public timeline shows the latest check, the last 24 hours, and the most recent important change. Watch keeps 30 days.
The notes above are for this connector.
Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
Tools and declared exposure
Server annotations are declarations, not verified behavior.
Show 2 of 2 server-provided tool definitions
web_fetch_exa
Declared read-onlyShow server-provided detailsServer description (copied; language not verified)
Read a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL.
Best for: Extracting full content from known URLs. Batch multiple URLs in one call.
Returns: Clean text content and metadata from the page(s).
Input schema (server-provided preview — do not copy)
Declared read-onlyShow server-provided detailsServer description (copied; language not verified)
Search the web for any topic and get clean, ready-to-use content.
Best for: Finding current information, news, facts, people, companies, or answering questions about any topic.
Returns: Clean text content from top search results.
Query tips:
describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue".
Use category:people / category:company to search through Linkedin profiles / companies respectively.
If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
Input schema (server-provided preview — do not copy)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"objective",
"query"
],
"properties": {
"query": {
"type": "string",
"minLength": 1,
"description": "Natural language search query. Should be a semantically rich description of the ideal page, not just keywords. Optionally include category:<type> (company, people) to focus results — e.g. 'category:people John Doe software engineer'."
},
"objective": {
"type": "string",
"maxLength": 4096,
"minLength": 1,
"description": "Goal for this search turn; say which documents should rank first, which should be excluded, and what specific facts or figures to pull from them."
},
"numResults": {
"type": "number",
"description": "Number of search results to return (default: 10)."
}
},
"additionalProperties": false
}
Evidence and limitations
Method: anonymous Streamable HTTP probe. We never invoke a tool.
Attempted protocols: 2026-07-28, 2025-11-25
Protocol2025-11-25
TransportStreamable HTTP
AuthNo authentication challenge observed
EvidencePublic contract observed
Total latency3141 ms
Response bytes2441
No diagnostic errors.
Observation history
Operational
· stable since
2025-11-25 · 2 tools · no change · 58 checks
Operational
2025-11-25 · 2 tools
Operational
2025-11-25 · 2 tools
Complete public contract · 2025-11-25 · 2 tools
417745203f67
Complete public contract · 2025-11-25 · 2 tools
417745203f67
Complete public contract · 2025-11-25 · 2 tools
417745203f67
Deep monitoring eligibility
Eligible for deep monitoring
A complete public tools/list contract was observed, so a future deep-monitoring baseline can be compared safely.
Personal Watch is not open yet. This report does not start a Watch or a payment.