CitePulse: Academic citation analytics for AI research agents, grant offices, and PIs — bibliography verification, retraction detection, paper/author/institution/journal metrics, topic and funder impact scans, and grounded literature briefs. Built on open scholarly infrastructure (OpenAlex, Cross...
AI agents call citepulse to retrieve information from Pulsenetwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
doi | string | — | DOI (preferred, exact match) |
lang | string | — | Response language, default en |
name | string | — | Author name to search |
title | string | — | Paper title (used only if doi is omitted) |
topic | string | — | Topic/field name or keyword |
years | string | — | Lookback window in years, default 3 |
action | string | Yes | Which endpoint to call. Options: ref-check | paper | author | institution | journal | topic-scan | funder-impact | literature-brief |
funder | string | — | Funder name |
question | string | — | The research question to synthesize |
citations | string | — | Comma-separated list of DOIs and/or free-text references, up to 20 items. |
compare_to | string | — | Optional second institution name for a side-by-side benchmark |
openalex_id | string | — | OpenAlex author ID for an exact, disambiguated lookup |
Parameters from the server's own tool schema.
This tool exclusively retrieves and analyzes academic metadata—it reads bibliographic data, metrics, and institutional research information without creating, modifying, or deleting records.
From the tool's definition CitePulse provides 'bibliography verification, retraction detection, paper/author/institution/journal metrics, topic and funder impact scans, and grounded literature briefs.' All endpoints (ref-check, paper, author, institution) are lookup and analytics…
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
CitePulse: Academic citation analytics for AI research agents, grant offices, and PIs — bibliography verification, retraction detection, paper/author/institution/journal metrics, topic and funder impact scans, and grounded literature briefs. Built on open scholarly infrastructure (OpenAlex, Crossref). All endpoints require x402 payment (USDC on Base mainnet) via the PAYMENT-SIGNATURE header. Coverage: Global Endpoints: • ref-check ($0.15): Bibliography verification (flagship) • paper ($0.05): Single-paper lookup • author ($0.10): Author metrics • institution ($0.15): Institution research-output benchmark • journal ($0.10): Journal/venue intelligence • topic-scan ($0.20): Rising-topic research scan • funder-impact ($0.20): Funder research-impact brief • literature-brief ($0.25): Grounded literature synthesis. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
citepulse accepts 12 parameters: doi, lang, name, title, topic, years, action, funder, question, citations, compare_to, openalex_id. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for citepulse: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pulsenetwork. Nothing to install.
citepulse is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the citepulse rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for citepulse. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
citepulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
citepulse is one line of Pulsenetwork's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →