Scopus (BYOK)

Scopus (BYOK) — connector documentation

• MCP endpoint: https://byok-scopus.connectorbay.com/mcp
• REST API: POST https://byok-scopus.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-scopus.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Scopus Elsevier API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-scopus.connectorbay.com/health · Tool schemas: https://byok-scopus.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-scopus · agent@connectorbay.com

What Scopus (BYOK) is for

Scopus (BYOK) lets an AI assistant read your own Scopus data through the Scopus API with a key you supply (Elsevier API key). Read-only: 10 tools (search_documents, search_authors, search_affiliations, get_abstract_by_scopus_id, get_abstract_by_pubmed_id, get_author_profile, get_author_by_orcid, get_affiliation_profile, search_serial_titles, get_serial_title_by_issn). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.elsevier.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Scopus. Scopus and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which highly cited papers on graphene batteries were published since 2022?"
• "Find the Scopus profile of researcher Maria Garcia at the University of Toronto"
• "Which institutions in Scopus are called 'Karolinska'?"
• "What are the details and citation count of Scopus document 84884919538?"
• "What is the Scopus citation count of PubMed article 11852050?"
• "What is the h-index and document count of Scopus author 7202909704?"

What it does

• search_documents: Search Scopus abstracts with a Boolean query (for example TITLE-ABS-KEY(...), AUTH(...), AFFIL(...), PUBYEAR > 2020). Returns title, authors, source, date, DOI and citation count.
• search_authors: Search Scopus author profiles by Boolean query (for example AUTHLASTNAME(smith) and AUTHFIRST(j), AFFIL(...), ORCID(...)) or list the co-authors of one author ID.
• search_affiliations: Search Scopus affiliation (institution) profiles by Boolean query such as AFFIL(university) or AF-ID(60016849).
• get_abstract_by_scopus_id: Get the Scopus record of a document by Scopus ID: title, source, date, DOI, citation count, authors, affiliations, keywords and subject areas (abstract text with view META_ABS).
• get_abstract_by_pubmed_id: Get the Scopus record of a document by its PubMed ID: title, source, date, DOI, citation count, authors and keywords.
• get_author_profile: Get a Scopus author profile by author ID: name, document count, citation counts, current affiliation and subject areas; view METRICS adds the h-index.
• get_author_by_orcid: Get a Scopus author profile by ORCID iD: name, document count, citation counts, current affiliation and subject areas.
• get_affiliation_profile: Get a Scopus affiliation profile by affiliation ID: name, address, city, country, author count and document count.
• search_serial_titles: Search journals, conference proceedings and book series indexed by Scopus by title, publisher, ISSN or subject area; includes open-access flags and metrics.
• get_serial_title_by_issn: Get the Scopus metadata of one journal or series by ISSN: publisher, type, subject areas, open-access flags and citation metrics (SNIP, SJR, CiteScore).

BYOK key

You bring your own Scopus Elsevier API key (https://dev.elsevier.com/apikey/manage). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.elsevier.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://dev.elsevier.com/sc_api_spec.html (the API this connector calls, with a BYOK key)

Live from the Scopus API (api.elsevier.com) with a BYOK key; documentation: https://dev.elsevier.com/sc_api_spec.html. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Scopus. Scopus and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Scopus account.

Built for: Worldwide. Languages: English.

Scopus (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Scopus (BYOK) is. Scopus (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Scopus data: Search Scopus documents, authors and affiliations and read abstracts, author profiles and journal metadata with your own Elsevier API key. You bring your own Scopus Elsevier API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Scopus call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.elsevier.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Scopus rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Scopus receives. The request we make on your behalf, including the key and the arguments, under Scopus's own terms and privacy policy. Scopus acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Scopus gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Scopus data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Scopus (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Scopus at any time to end all access.

Children. Scopus (BYOK) is a general-audience service operated by the adult using the assistant, under Scopus's own age rules.

Changes. We will post changes here with a new effective date.

Scopus (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Scopus (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Scopus (BYOK) provides: Search Scopus documents, authors and affiliations and read abstracts, author profiles and journal metadata with your own Elsevier API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Scopus credentials and only access data you are allowed to access. Scopus's terms apply to your use of Scopus; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Scopus. Scopus and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Scopus returns, lightly trimmed; it may be incomplete, delayed or changed by Scopus. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Scopus account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Scopus's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Scopus may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Scopus key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Scopus takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-scopus

Scopus (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-scopus.connectorbay.com/mcp
• REST API: https://byok-scopus.connectorbay.com/openapi.json
• Live status: https://byok-scopus.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Scopus (BYOK) never asks for them.