Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CiteMe

REMOTE · CITEME.APP · SCANNED AUG 6

Search papers, format citations in 60 styles, and verify bibliographies against scholarly sources.

Available components

69 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 719 tokens (~239/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · citeme.app

# add to Claude Code
claude mcp add --transport http app-citeme-citeme https://citeme.app/api/mcp
# ~/.codex/config.toml
[mcp_servers.app-citeme-citeme]
url = "https://citeme.app/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-citeme-citeme": {
      "type": "remote",
      "url": "https://citeme.app/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-citeme-citeme --url https://citeme.app/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  app-citeme-citeme:
    url: "https://citeme.app/api/mcp"
// mcp.json
{
  "mcpServers": {
    "app-citeme-citeme": {
      "type": "http",
      "url": "https://citeme.app/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Aug 26 0
    • Stability: unverified → 0.03 functional
  • 5 Aug 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Aug 2026 · Probed https://citeme.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=citeme.app CN=YE2,O=Let's Encrypt,C=US 25 Jun 2026 23 Sept 2026 ECDSA 256 ECDSA-SHA384 59b8e56d6a74951fdaa736a2a747562f5ac
SANs: *.citeme.app, citeme.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of citeme.app. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
citeme.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://www.googletagmanager.com https://*.paddle.com https://public.profitwell.com https://us-assets.i.posthog.com https://challenges.cloudflare.com https://accounts.google.com https://static.cloudflareinsights.com https://www.clarity.ms https://*.clarity.ms https://browser.sentry-cdn.com; style-src 'self' 'unsafe-inline' https://*.paddle.com https://public.profitwell.com https://fonts.googleapis.com; img-src 'self' data: blob: https://books.google.com https://covers.openlibrary.org https://*.supabase.co https://www.google-analytics.com https://www.googletagmanager.com https://*.clarity.ms https://c.bing.com; font-src 'self' data: https://fonts.gstatic.com https://use.typekit.net; connect-src 'self' blob: https://*.supabase.co https://auth.citeme.app https://us.i.posthog.com https://us-assets.i.posthog.com https://www.google-analytics.com https://analytics.google.com https://*.google-analytics.com https://*.googletagmanager.com https://
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://citeme.app/api/mcp Verified 200
http (plaintext) http://citeme.app/api/mcp HTTPS enforced 301 https://citeme.app/api/mcp
MCP tools — 3 exposed · ~373 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
check_references ~76

Verify a user-provided bibliography against scholarly sources and return match status, identifiers, and citation issues. Results may be cached for up to six hours and usage may be logged; the bibliography is not published or added to an account.

NameTypeReqDescription
textstringyesRaw bibliography text (one reference per line, or a full references section)

No output schema declared.

No examples provided.

format_citation ~162

Format citation data (title, authors, year, etc.) into a specific citation style. The formatted result may be stored in an operational cache; the tool does not publish content or modify a user account.

NameTypeReqDescription
authorsarrayyesAuthor names (e.g., ["John Smith", "Jane Doe"])
doistringDOI identifier
pagestringPage range (e.g., "123-456")
publisherstringPublisher name
stylestringCitation style
titlestringyesPaper/book title
urlstringURL of the source
venuestringJournal or venue name
volumestringVolume number
yearyesPublication year

No output schema declared.

No examples provided.

search_citations ~135

Search scholarly sources by topic, title, author, DOI, or ISBN and return matching works as formatted citations. Resolved works may be merged into CiteMe's shared scholarly catalog and operational caches; the tool does not publish content or modify a user account.

NameTypeReqDescription
limitnumberNumber of citations to return
querystringyesSearch query: topic, title, author name, DOI, or ISBN
source_typestringType of source to search for
stylestringCitation style (e.g., apa, abnt, mla, vancouver, chicago-author-date, ieee)

No output schema declared.

No examples provided.