BARK Regulatory Research

tech.barktechnologiesPublished by barktechnologies.techOfficial publisherv1.0.0Updated Nov 4, 2026

EU banking regulation research, cited to the article, from a versioned knowledge graph.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Remote MCP server that lets an assistant research EU banking regulation, with answers cited down to the article from a versioned knowledge graph.

What you can do
  • Research EU banking regulation through a versioned knowledge graph.
  • Retrieve regulatory material with citations to the specific article.
  • No tool list is published, so the exact operations are not documented; expect question-answering and lookup over the regulatory corpus.
When to use it
Useful when an assistant needs to answer questions about EU banking rules and the answer must point to the exact article rather than a general summary, and when it matters that the cited text comes from a specific version of the regulation.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. OAuth authentication is required, so the user must sign in with an account accepted by the provider. No environment variables or headers are declared.
Before you install
Access is gated by OAuth, so the assistant acts under the signed-in user's account. The tool list is not published, so what the server can read or change is unknown before connecting. Regulatory content is a research aid, not legal advice, and citations should be checked against the official text.

Installation

In SourceWeft

  1. Open BARK Regulatory Research 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/tech.barktechnologies%2Fbark/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": {
    "bark-regulatory-research": {
      "type": "http",
      "url": "https://mcp.barktechnologies.tech/mcp"
    }
  }
}

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. v1.0.0LatestNov 4, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.