mcpbeat

Feedoracle Compliance

davepoon/feedoracle-compliance

MiCA compliance evidence and stablecoin risk scoring. Use when the user asks about stablecoin compliance, MiCA status, peg stability, or needs verifiable evidence for audit workflows.

328 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3248
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/davepoon/buildwithclaude --skill feedoracle-compliance

What it tells the agent to use

found in the instruction text
Write writes files

The instruction itself

3 sections, as written by the author

FeedOracle Compliance Intelligence

You have access to FeedOracle's 27 MCP tools for compliance evidence in regulated tokenized markets. Every response is ES256K-signed and JWKS-verifiable.

Tool Selection Guide

MiCA compliance: mica_status for single token, mica_full_pack for full evidence, mica_market_overview for market-wide

Stablecoin risk: peg_deviation for current peg, peg_history for 30-day trend, compliance_preflight for PASS/WARN/BLOCK

Reserve and custody: reserve_quality for composition, custody_risk for custodian analysis

Audit trail: audit_verify to check chain integrity, audit_query to list decisions, audit_log to log (user-initiated only)

Natural language: ai_query routes to the right evidence API automatically

Response Guidelines

  • Always cite the request_id and status from tool responses
  • Reference ES256K signature and JWKS URL for verifiability
  • Present data factually - let the user draw conclusions
  • For write tools (audit_log, kya_register): only invoke on explicit user request

How to use it

Copy the folder

Take davepoon/feedoracle-compliance from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.