Fillin
Server Details
Search for AI agents. Closes the LLM-cutoff gap: CVEs, papers, frontier AI, prediction markets.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
8 toolsfillin_answerInspect
Synthesized post-cutoff answer with inline citations.
Use this when your model is small / cheap / weaker at tool-result
synthesis (Llama, Gemini Flash, Mistral, Nemotron, Qwen). Fillin runs
a server-side LLM pass over the retrieved post-cutoff documents and
returns a 150-250 word answer with [title](url) citations already
embedded — you can quote it directly.
Premium models (Opus, Sonnet, GPT-4o) usually get better results from
`fillin_query` and synthesizing themselves, but this tool works for
any caller. Costs more than fillin_query because of the synthesis pass.
Returns:
A dict with:
- answer: the synthesized paragraph (str | None)
- citations: list of {title, url} extracted from the answer
- corpus_match: "strong" | "weak" | "none" — quality of retrieval
- top_score: float — top reranked similarity score
- model: the synthesizer model used (e.g. claude-haiku-4-5)
- reason: set when answer is None (e.g. "no_relevant_docs")
- results: raw post-cutoff documents (same shape as fillin_query)
- cutoff, query, gap_days: echoes for context| Name | Required | Description | Default |
|---|---|---|---|
| k | No | Number of documents to ground the answer in (1-20). | |
| query | Yes | Natural-language question, max 512 chars. | |
| cutoff | Yes | Training cutoff as ISO-8601 date (e.g. 2026-01-01). |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
fillin_healthInspect
Liveness + freshness — host, total docs, earliest, latest. No auth required.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
fillin_queryInspect
Retrieve documents published after a training cutoff, ranked by similarity.
Call this whenever the user asks about events, releases, papers, issues,
or news that might post-date your training data. Fillin only returns
documents published AFTER `cutoff`, so nothing returned is redundant
with what the model already knows.
Args:
query: Natural-language search query (e.g. "rust async runtimes").
Max 512 characters.
cutoff: ISO-8601 date representing the agent's training cutoff
(e.g. "2026-01-01"). Documents on or before this date are
excluded from results.
k: Number of documents to retrieve, 1-20. Defaults to 5.
Returns:
A dict with:
- cutoff: echoed cutoff (ISO timestamp)
- query: echoed query
- gap_days: days between cutoff and now
- results: list of {id, source, url, published_at, title, text, score}| Name | Required | Description | Default |
|---|---|---|---|
| k | No | Number of documents to retrieve (1-20). | |
| query | Yes | Natural-language search query, max 512 chars. | |
| cutoff | Yes | Training cutoff as ISO-8601 date (e.g. 2026-01-01). Documents on or before this date are excluded. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
fillin_statsInspect
Get corpus stats — total docs, date range, freshness.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
query_cvesInspect
Daily snapshot of CVE / supply-chain advisories from NVD, GitHub Security Advisories, and OSV. Use before merging dependency updates, when triaging an alert, or when a user asks "is package X compromised".
Each result row carries a structured `affected` list (one entry per
affected package: ecosystem, name, vulnerable_range, patched_range) and
a numeric `severity_score` (CVSS baseScore, nullable on OSV-only rows).
A buyer can act on the returned row — pin to `patched_range` — without
a second hop to NVD or GHSA.| Name | Required | Description | Default |
|---|---|---|---|
| k | No | 1-20 | |
| query | Yes | Vulnerability / supply-chain query. | |
| cutoff | Yes | Training cutoff as ISO-8601 date. | |
| min_severity | No | Optional CVSS baseScore floor (0.0-10.0). When set, rows with a populated severity_score below this value are dropped, and rows whose severity is unknown are skipped. Use 7.0 for high+critical only, 9.0 for critical only. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
query_frontierInspect
Daily snapshot of frontier AI lab announcements + HuggingFace trending model releases. Sources: OpenAI / DeepMind / Meta / Mistral blog RSS, Anthropic + HF blogs (via shared rss corpus), and the HF trending models API. Use when a user asks "what model dropped" or "did announce X".
| Name | Required | Description | Default |
|---|---|---|---|
| k | No | 1-20 | |
| query | Yes | Frontier-lab / model-release query. | |
| cutoff | Yes | Training cutoff as ISO-8601 date. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
query_marketsInspect
Active prediction markets across Polymarket, Kalshi, Manifold, and Metaculus. Use when a user asks "is there a market on X", "what odds is the market giving Y", or before any agent action that should be informed by a market price.
Each result row carries the question, venue, close date, volume, and
a first-sight price snapshot embedded in `text`. Prices in the corpus
are point-in-time at first ingestion — for live pre-trade pricing,
follow the `url` to the venue and read the current quote there.| Name | Required | Description | Default |
|---|---|---|---|
| k | No | 1-20 | |
| query | Yes | Prediction-market / forecast query. | |
| cutoff | Yes | Training cutoff as ISO-8601 date. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
query_papersInspect
Daily snapshot of new research relevant to AI/ML/agents. Union of arXiv (cs.AI/cs.LG/cs.CL/cs.CR/cs.DC), HuggingFace daily papers (with upvote signal in title), and bioRxiv. Use when a user asks about a new technique, paper, or benchmark.
| Name | Required | Description | Default |
|---|---|---|---|
| k | No | 1-20 | |
| query | Yes | Research / paper query. | |
| cutoff | Yes | Training cutoff as ISO-8601 date. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!