compare_data_feeds

MCP tool from Nexus Agents by nexus-substrate

Diff two YAML/JSON feeds: coverage + per-field axes

How to use it

Project documentation lists compare_data_feeds for the Nexus Agents MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.

Install Nexus Agents

$npm install -g nexus-agents

FULL NEXUS AGENTS LISTING

Other tools in Nexus Agents (39)

cancel_job

Mark an async-mode job as cancelled — idempotent (#3042 Stage 1b)

ci_health_check

CI infrastructure health — composes GitHub status + recent-runs activity (#3076)

consensus_vote

Multi-model consensus voting on proposals

create_expert

Create a specialized expert agent

delegate_to_model

Pick the best-fit existing model for a task (no registry change)

execute_expert

Run a task through a previously-created expert (by expertId)

execute_spec

Execute AI software factory spec pipeline

extract_symbols

TypeScript-compiler-API AST symbols from a SINGLE file (functions/classes/types)

get_job_result

Read result of an async-mode dispatch by jobId (#3042 / #2631)

issue_triage

Triage GitHub issues with trust classification

list_experts

Inventory of expert ROLES for createexpert

list_jobs

List async-mode jobs across all tools — cross-session discovery (#3046 / #2631)

list_workflows

Inventory of multi-step TEMPLATES for runworkflow

memory_query

Query across all memory backends

memory_stats

Memory system statistics dashboard

memory_write

Write to typed memory backends

orchestrate

Task orchestration with Orchestrator coordination

query_task_state

Query the structured task-state log for a task ID

query_trace

Query execution traces for observability

registry_import

Draft YAML for a NEW model entry (for picking existing models use delegatetomodel)

repo_analyze

Analyze GitHub repository structure

repo_security_plan

Generate security scanning pipeline for a repo

research_add

Add an arXiv PAPER to the registry (for non-paper sources use researchaddsource)

research_add_source

Add a NON-PAPER source (repo/tool/blog) — for arXiv papers use researchadd

research_analyze

Analyze registry for gaps, trends, coverage

research_catalog_review

Review auto-cataloged research references

research_discover

Discover papers/repos from external sources

research_query

Query research registry (status, overlap, stats, search)

research_synthesize

Synthesize registry into topic clusters with themes

run_dev_pipeline

Full dev pipeline: research, plan, vote, implement, QA

run_graph_workflow

Run a DAG workflow with per-node checkpoints + audit trail (linear → runworkflow)

run_pipeline

Execute a pipeline plugin by name with typed input

run_workflow

Run a linear workflow template (use rungraphworkflow for DAGs)

search_codebase

Cross-file search over declared symbol NAMES (declarations only, not usages)

search_usages

Structural usage/call-site search for a symbol via ast-grep (calls, member calls, new, imports, references) — the "where is X used" gap searchcodebase cannot fill

survey_oss_landscape

Transient OSS project search (license, stars, last-commit) via GitHub

vendor_publishing_audit

Look up a vendor's signing infrastructure (GPG keys, URL patterns, signature shape)

verify_audit_chain

Verify hash chain of a FileAuditStorage audit log directory

weather_report

Multi-CLI performance weather report