_ registry / mcp streamable-http · checked 2h ago

pubscope

https://pubscope.org

Registry code: 4b1705b5c94ceeb6

api record

PubScope provides verified intelligence on 46,000+ academic journals. Use search_journals to find journals by name/ISSN/publisher, get_journal for one profile, compare_journals for a side-by-side, and check_citations to verify a reference list. All data comes from open academic databases and every signal links back to its source.

WHAT YOU GET: journal identity, publisher, indexing status (Web of Science, Scopus, DOAJ), SJR quartile and scope are always returned. Trust Score, Journal Impact Factor, APC amount, acceptance rate and measured submission-to-publication time are returned only to an…

endpoint
https://pubscope.org/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pubscope live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is pubscope free to use?
Yes — the hub reached it with no key and no payment.
What tools does pubscope have?
4 tools: get_journal, check_citations, compare_journals, search_journals.
Is pubscope safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.1%

90 days 99.2%· all time 99.2%

latency
538ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 369 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search academic journals by title or issn
  • get a journal's indexing and quartile
  • compare academic journals
  • verify a reference list
takes → gives
text, documents → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_journals reads open 5h ago

    Search 46,000+ academic journals by title, ISSN, or publisher. Returns indexing status (WoS/Scopus/DOAJ), SJR quartile and open-access info for any caller; trust score and APC require an identified caller. Supports filters.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Journal title, ISSN (e.g. 0028-0836), or publisher name"
        },
        "quartile": {
          "type": "string",
          "description": "Optional SJR quartile filter: Q1, Q2, Q3 or Q4"
        },
        "max_results": {
          "type": "integer",
          "description": "Max results to return (1-20, default 10)"
        },
        "open_access_only": {
          "type": "boolean",
          "description": "Only return Open Access journals"
        }
      }
    }
    arguments 24 lines
  • get_journal reads unknown 13h ago

    Full profile of one journal by ISSN: indexing, quartile, open-access status, scope and integrity signals (e.g. DOAJ withdrawal) for any caller. Trust score with breakdown, impact factor, APC and measured publication time require an identified caller. Use when the user asks about one journal.

    mcp-tool

    {
      "type": "object",
      "required": [
        "issn"
      ],
      "properties": {
        "issn": {
          "type": "string",
          "description": "The journal's ISSN, e.g. 1361-8415"
        }
      }
    }
    arguments 12 lines
  • check_citations reads unknown 5h ago

    Verify a pasted reference list (plain text, BibTeX or RIS) against Crossref, OpenAlex, DataCite, Semantic Scholar, arXiv, PubMed and DBLP, plus Retraction Watch. Flags references that cannot be found (possibly fabricated), retracted papers and DOI mismatches. One check per day without an account; sign in for more.

    mcp-tool

    {
      "type": "object",
      "required": [
        "references"
      ],
      "properties": {
        "references": {
          "type": "string",
          "description": "The reference list text, one reference per line"
        }
      }
    }
    arguments 12 lines
  • compare_journals reads unknown 5h ago

    Side-by-side comparison of 2-4 journals by ISSN: quartile and indexing for any caller, trust score and APC for an identified one.

    mcp-tool

    {
      "type": "object",
      "required": [
        "issns"
      ],
      "properties": {
        "issns": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "2-4 ISSNs to compare, e.g. [\"1361-8415\", \"1533-7928\"]"
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4b1705b5c94ceeb6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4b1705b5c94ceeb6/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4b1705b5c94ceeb6/badge.svg)](https://brick.blue/agent/4b1705b5c94ceeb6?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.