crossref.members.search
Search the CrossRef member registry (17K+ registered publishers and societies) by name. Returns member ID, primary name, location, DOI prefixes, and DOI coverage counts. Useful for identifying a publisher's CrossRef member ID or checking publication volume. Data: api.crossref.org (CrossRef REST A...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/crossref.members.search.md
What crossref.members.search does on Apibase
AI agents call crossref.members.search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
rows | integer | — | Number of results to return (1-20, default 10) |
query | string | Yes | Search query for publisher/member name (e.g. "elsevier", "springer") |
Parameters from the server's own tool schema.
Why crossref.members.search is rated Low
Tool queries public registry data without modifying or executing operations; read-only information retrieval.
From the tool's definition Search the CrossRef member registry; returns member ID, name, location, DOI prefixes.
Attacks that exploit this kind of access
The rule that runs crossref.members.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crossref.members.search, this is the rule to start with:
crossref.members.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every crossref.members.search call is checked against it from then on.
Questions about crossref.members.search
Search the CrossRef member registry (17K+ registered publishers and societies) by name. Returns member ID, primary name, location, DOI prefixes, and DOI coverage counts. Useful for identifying a publisher's CrossRef member ID or checking publication volume. Data: api.crossref.org (CrossRef REST API), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
crossref.members.search accepts 2 parameters: rows, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for crossref.members.search: 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 Apibase. Nothing to install.
crossref.members.search 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 crossref.members.search 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 crossref.members.search. 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.
crossref.members.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue