Concord

io.github.jeswrPublished by GitHub account jeswrv0.1.0Updated Nov 4, 2026

Read, query and check data against ODI standards hub ontologies (OWL, LinkML), and report gaps.

The publisher's own server: Concord

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Remote MCP server that lets an assistant read, query and check data against ODI standards hub ontologies (OWL, LinkML) and report gaps.

What you can do
  • Read and query ODI standards hub ontologies expressed in OWL and LinkML
  • Check data against those ontologies
  • Report gaps found when data does not match the standards
  • No individual tools are listed in the manifest, so exact operations are not documented.
When to use it
Useful when working with ODI standards hub ontologies and you want an assistant to look up definitions, validate datasets against them, or surface where data falls short of the standard.
Requirements
A remote MCP endpoint at standards-concord.vercel.app over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Access requires OAuth sign-in, so the server receives your account identity. The manifest lists no tools, so what it can read or change is not documented; review the provider's terms before connecting.

Installation

In SourceWeft

  1. Open Concord in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.jeswr%2Fconcord/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "concord": {
      "type": "http",
      "url": "https://standards-concord.vercel.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestNov 4, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Concord integrations