research_with_sources
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@research_with_sourcesResearch these sources and provide cited findings in English."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Research Scout Provider
Independent English/Spanish TypeScript provider that turns caller-supplied source metadata and excerpts into deterministic, traceable research fixtures. It exposes an HTTP API and an MCP-shaped stdio tool.
Proveedor TypeScript independiente en inglés/español que convierte metadatos y extractos proporcionados por el cliente en resultados de investigación deterministas y trazables. Expone una API HTTP y una herramienta MCP por stdio.
This service does not fetch source URLs or perform live fact-checking. It never contacts Stellar Bazaar. The public deployment is a standalone demonstration endpoint.
Live deployment: https://research-scout-provider.vercel.app
Public API
After deployment, the following routes are available:
Method | Route | Purpose |
|
| Provider metadata and route discovery |
|
| Health and operating-mode status |
|
| Produce cited findings from supplied sources |
Example request:
curl -X POST "$PROVIDER_URL/v1/research" \
-H "content-type: application/json" \
-d '{
"query": "What is Stellar used for?",
"locale": "en",
"maxSources": 5,
"sources": [{
"title": "Example source",
"url": "https://example.com/article",
"excerpt": "Caller-provided evidence.",
"publisher": "Example",
"publishedAt": "2026-01-01T00:00:00Z"
}]
}'The response contains summary, individually cited findings, normalized citations, explicit limitations, and mode: "local_fixture". Select Spanish with "locale": "es".
La respuesta incluye summary, findings con citas individuales, citations normalizadas, limitations explícitas y mode: "local_fixture". Usa "locale": "es" para español.
Input limits
Query: 2–500 characters.
Sources: 1–25 entries; only HTTP(S) URLs are accepted.
Source title: up to 300 characters; excerpt: up to 2,000 characters.
maxSources: 1–10, default 5.Local Node server request body: maximum 64 KiB.
No credentials, wallet data, payment data, or secrets should be submitted.
Local development
Requires Node.js 20 or newer.
npm ci
npm run check
npm startThe local HTTP server listens on http://127.0.0.1:8787. To run MCP over stdio after building:
npm run build
npm run start:mcpThe MCP tool is named research_with_sources. Its input and output contract matches the HTTP endpoint.
Deploy to Vercel
This repository includes vercel.json and three serverless entry points under api/. Deploy it as a separate Vercel project:
npx vercel
npx vercel --prodNo environment variables are required. Vercel rewrites /, /health, and /v1/research to their corresponding serverless functions.
Safety and data policy
No outbound network requests or browser automation.
No persistence, authentication, payments, wallets, or credential handling.
Stable source IDs are derived from source URLs with SHA-256 when omitted.
Output synthesizes only caller-supplied text and is not independent verification.
No integration with or publication to Stellar Bazaar.
See service-card.json for machine-readable discovery.
License
Apache License 2.0. See LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Read-only MCP over an agentic SLR workspace with per-claim citation verification
Read-only MCP over an agentic SLR workspace with per-claim citation verification
Auditable MCP server for PubMed, Europe PMC, ClinicalTrials.gov, and bioRxiv/medRxiv queries
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CaBsCrypto/research-scout-provider'
If you have feedback or need assistance with the MCP directory API, please join our Discord server