Bgpt Paper Search
Searches BGPT scientific papers by topic or DOI and retrieves claim-level evidence...
Install
npx skills add K-Dense-AI/scientific-agent-skills --skill bgpt-paper-search -g -a claude-code -y- Repository
- K-Dense-AI/scientific-agent-skills55.7k
- Category
- Data and ML
- Updated
- 9d ago
- License
- MIT
- Context cost
- Mediumabout 1,806 tokens
- Runs scripts
- No, instructions only
What it does
Searches BGPT scientific papers by topic or DOI and retrieves claim-level evidence extracted from full text, including experiments, reported statistics, scope, limitations, and provenance. Use for literature reviews, evidence synthesis, and finding experimental details beyond abstracts.
BGPT Paper Search
When to use
Use BGPT to find full-text-derived evidence for a research question or a known DOI. It returns extracted claims and their supporting experiments, rather than only bibliographic metadata. Use these records to build a traceable evidence table; they are not a complete systematic-review search or a validated risk-of-bias assessment.
Connect
Configure BGPT in the host before use; installing this skill does not register an MCP server. The provider supports both transports:
| Transport | Endpoint |
|---|---|
| Streamable HTTP | https://bgpt.pro/mcp/stream |
| SSE | https://bgpt.pro/mcp/sse |
Use the host's native remote-MCP configuration when supported. For a host that
uses mcpServers JSON and requires a local stdio bridge, this configuration uses
mcp-remote (adapt it to the host's actual settings format):
{
"mcpServers": {
"bgpt": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://bgpt.pro/mcp/stream", "--transport", "http-only"]
}
}
}
The published bgpt-mcp 1.1.0 npm package is a thin SSE wrapper around
mcp-remote, not a local paper database. Its bundled README predates the current
tool contract and pricing. Prefer the native connection or configurable bridge
above. The linked BGPT GitHub repository was unavailable at review time; use
the current provider documentation and live tool schema.
Free access needs no key. For paid usage, configure Authorization: Bearer <key>
in the host's remote-server headers, using its credential storage. For the bridge,
mcp-remote supports --header-file
with a local credential file. Do not put api_key in an MCP tool call: neither
current tool declares that argument. Authenticate through the connection.
Search and DOI lookup
Discover the connected server's tools before calling them. The live BGPT 2.14.7 schema reviewed on 2026-09-30 exposes:
