OmniSeek MCP server

Read from the package source without running it. The installed server may list more.

• _set_limiter
• omniseek_coauthors

  Use WHEN you want WHO a researcher collaborates with — advisor + closest collaborators by joint-paper count, or how a paper's author group is connected (WebSearch cannot build this). One LAYER, not the whole graph — co-authorship is one edge type; YOU overlay the others (advising, institution cohort, citation, code, social) and judge what each connection MEANS.

• omniseek_curator_act
• omniseek_curator_view

  Use WHEN running the source-curation protocol (judge the admission queue or a source audit) — READ curator state: queue | packet | audit. Never mutates. Pick a view with ``what``:

• omniseek_field_skeleton
• omniseek_gatherwrite action

  Run N independent read-only eye tools IN PARALLEL, returning results in one response.

• omniseek_graph
• omniseek_institution_cohort

  Use WHEN you need the people-ROSTER of a lab / department / university (who actively publishes there, optionally scoped to a field) — the "who's at this lab" question, orthogonal to co-authorship ("same lab, never co-authored" is still a tie, and the people-roster of a target lab is exactly the SG/Canada cohort question).

• omniseek_paper_enrich

  Use WHEN you need ONE paper's open-access full-text PDF, retraction / integrity status, or citation count — signals omniseek_search / field_skeleton do NOT give cleanly. Keyless, mechanical: YOU decide when + on which papers.

• omniseek_paper_recommend

  Use WHEN you have a paper and want more like it — semantically-similar papers (SPECTER embeddings) that keyword search and the citation graph miss, including very recent work. Uses Semantic Scholar's recommendation model (SPECTER embeddings + co-citation), so it surfaces conceptually-related work that omniseek_search (keyword) and omniseek_field_skeleton (citations) miss — including very recent pa

• omniseek_read
• omniseek_resolve_identity

  Resolve a PERSON's name to candidate author ids — the shared front door for EVERY relationship layer (you must know WHICH person before you can map their connections).

• omniseek_ruling

  Use WHEN two graph nodes ARE (or are NOT) the same person / entity and you want views to collapse them — record / list / retract same_as | not_same_as rulings (the one judgment channel the graph's working policy applies).

• omniseek_search
• omniseek_sensor

  Use WHEN you want to MONITOR a query over time and be told only what's NEW — standing queries with novelty detection. ONE verb; ``action`` picks what to do.

• omniseek_sources
• omniseek_statement
• omniseek_transcribe
• omniseek_view

• Code scan220 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

92/100

higher than 90% of 4,460 AI and agents servers

Tools

19

the typical AI and agents server has 6

Tools that change things

5%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

69

more than 93% of 2,711 AI and agents servers

Downloads a week

55

more than 46% of 1,538 AI and agents servers with a package

OmniSeek: common questions

Is OmniSeek MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the OmniSeek safety report

How do I install OmniSeek?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does OmniSeek need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is OmniSeek maintained?

The last commit was 32 days ago (2026-10-03). The latest release is v0.2.1.

What can I use instead of OmniSeek?

Servers from other publishers that do the same job: SuperCompress MCP server, Agent Sniper MCP server and Mnemoverse Memory MCP server.

How does OmniSeek compare with other AI and agents MCP servers?

safety score 92/100 (higher than 90% of 4,460 AI and agents servers); tools 19 (the typical AI and agents server has 6); tools that change things 5% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.