timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
LLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.
Skills that teach the AI this kind of work; they work alongside this one
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 7/100 |
Quality: Passed 3/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/5 checks · Runs on your computer
We hid some of the commands
Connect by URL: the server address did not answer when we checked
No install path has passed yet. See the maker’s instructions or pick another server in this category · Maker’s install instructions · Others in this category
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect Agentsearch MCP yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
ChatGPT cannot connect Agentsearch MCP yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
Claude Code cannot connect Agentsearch MCP yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
Cursor cannot connect Agentsearch MCP yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
VS Code cannot connect Agentsearch MCP yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
No install path has passed yet. See the maker’s instructions or pick another server in this category
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Tool names and descriptions exactly as the server reported them on Nov 16, 2026. The maker wrote them, not us; we show them as plain text.
web_searchSearch the web via a provider-abstracted backend (Brave or Serper, configured operator-side). Returns normalized results, each with position, title, url, snippet, source, and domain, plus a meta envelope (cache state, provider, took_ms). Returns a provider_required error if no se
instant_answerDuckDuckGo Instant Answer API — definitions, entities, and quick facts. Returns a normalized answer with heading, type (abstract/answer/disambiguation), source, sourceUrl, optional image/definition, and relatedTopics, plus a meta envelope. Not a full web SERP; use web_search for
fetch_urlFetches any public http(s) URL, strips boilerplate (scripts, nav, footer, ads), and returns clean text or markdown ready for an LLM context window. SSRF-guarded — refuses private/loopback/internal hosts. Returns url, title, format, length, content (and finalUrl when redirected, p
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account IsaiahDupree, which owns the repo
Code last changed 31 days ago
No licence file found in the repo
Did not respond within 6 seconds when we checked
Did not respond within 6 seconds when we checked
Read 3 tool descriptions and found no hidden instructions to the AI
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/isaiahdupree-agentsearch-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 31 days ago, and the latest version (1.0.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
Search and read Empryo's documentation. Read-only, no auth, no local access.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| This one Agentsearch MCP | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | Yes | Yes | No | No |
| Basic checks | 3/5 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| License | – | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A remote MCP (Model Context Protocol) connector for AgentSearch API — an LLM/MCP-native web toolkit for agents and RAG pipelines: web search (provider-abstracted SERP), keyless instant answers, and URL → clean text/markdown fetch ready for an LLM context window.
Live: https://agentsearch-mcp.vercel.app/mcp — 3 tools, one per AgentSearch /v1 endpoint. Since the upstream AgentSearch deployment is metered (RapidAPI/Apify) and gates /v1/* behind a RapidAPI proxy-secret guard, this connector authenticates its own outbound calls with that same secret (AGENTSEARCH_MCP_PROXY_SECRET, sent as the X-RapidAPI-Proxy-Secret header) and applies a soft per-IP rate limit (AGENTSEARCH_MCP_RATE_LIMIT, default 30 tool-calls/hour, in-memory) so the free MCP tier stays a discovery channel rather than an unmetered bypass of the paid listing — see lib/ratelimit.js.
AgentSearch API is a plain REST API. Any HTTP client can already call it directly. This repo exists because MCP clients (Claude, ChatGPT, and other MCP-aware agents) don't consume arbitrary REST APIs — they consume MCP tools. agentsearch-mcp is a thin adapter layer that:
/mcp endpoint, so it can be registered as a connector in Claude, ChatGPT, or any other MCP client with one URL.fetch to AgentSearch, and the JSON response AgentSearch returns is handed back verbatim as the tool result.This connector is a free discovery/growth tier in front of the metered AgentSearch API. The upstream (agentsearch-api.vercel.app) is sold on RapidAPI/Apify; this MCP wrapper authenticates to it with the shared RapidAPI proxy secret and caps usage per-IP so it stays a taste-test rather than an unmetered path around the paid plans. Heavy/production volume should go through AgentSearch on RapidAPI/Apify.
AgentSearch's data has no per-user dimension — it's public web data (SERP results, DuckDuckGo instant answers, cleaned page text). There is nothing to gate per-caller, so this connector intentionally ships with:
api/mcp.js builds a fresh, stateless McpServer per request and serves it with zero MCP-caller auth checks. The only outbound auth is the upstream RapidAPI proxy secret described above, which the connector holds server-side.
One tool per AgentSearch /v1 endpoint (from agentsearch-api/openapi.yaml; /api/health is intentionally not wrapped):
| Tool | AgentSearch endpoint | Description |
|---|---|---|
web_search | GET /v1/search | Web SERP via a provider-abstracted backend (Brave or Serper). Returns normalized results with position/title/url/snippet/domain. |
instant_answer | GET /v1/answer | Keyless DuckDuckGo instant answer — definitions, entities, quick facts. |
fetch_url | GET /v1/fetch | Keyless, SSRF-guarded URL → clean, boilerplate-free text or markdown for RAG. |
All 3 tools are read-only and annotated { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true } — none of them write anything, and all of them reflect live, externally-changing web data.
Each tool handler does a plain fetch(\${AGENTSEARCH_MCP_API_BASE_URL}${path}\, ...) against the real AgentSearch REST API and returns the parsed JSON as MCP tool-result content:
{ content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] }
The outbound request carries X-RapidAPI-Proxy-Secret: so it passes the upstream guard on /v1/*. Upstream HTTP errors (4xx/5xx) are caught and surfaced as a typed MCP error result via an asError helper rather than crashing the request.
| Var | Default | Purpose |
|---|---|---|
AGENTSEARCH_MCP_API_BASE_URL | https://agentsearch-api.vercel.app | Upstream AgentSearch base URL (override for local/self-hosted testing). |
AGENTSEARCH_MCP_PROXY_SECRET | _(empty)_ | RapidAPI proxy secret, sent as X-RapidAPI-Proxy-Secret to pass the upstream /v1/* guard. Without it, guarded routes return 403. |
AGENTSEARCH_MCP_RATE_LIMIT | 30 | Soft per-IP tools/call cap per hour (in-memory, per serverless instance). |
api/mcp.js MCP endpoint (StreamableHTTPServerTransport, stateless, no MCP-caller auth)
api/health.js GET /api/health lib/tools.js All 3 tool definitions (zod schemas + fetch-and-forward handlers, proxy-secret auth) lib/ratelimit.js Soft per-IP tools/call rate limiter local-server.js Plain-Node http server for local dev / smoke testing (not deployed) test/smoke.mjs Real end-to-end smoke test (initialize, tools/list, tools/call) vercel.json Routes /mcp -> api/mcp.js, /health -> api/health.js server.json MCP registry manifest
npm install
npm run dev # starts local-server.js on :3900 npm run smoke # runs test/smoke.mjs against the local server
To exercise a real end-to-end fetch through the upstream guard, set the proxy secret first:
export AGENTSEARCH_MCP_PROXY_SECRET=<the RapidAPI proxy secret>
npm run dev & npm run smoke