
Compliance Auditor MCP
io.github.firasmosbehiPublished by GitHub account firasmosbehiv0.1.0Updated Oct 24, 2026
City hiring-compliance MCP server with regulation search and full audit risk scoring.
Overview
Lets an assistant search city hiring regulations and produce full audit risk scores through a hosted compliance-auditor endpoint.
- What you can do
- This remote MCP server is described as a city hiring-compliance server that combines regulation search with full audit risk scoring. It is intended to help an assistant look up hiring-related regulations and evaluate compliance risk. The manifest does not list individual tools, so the exact operations are not documented here.
- When to use it
- Relevant when an assistant needs to check city hiring regulations or assess hiring-compliance risk for an audit. It suits compliance, HR or legal workflows that need regulation lookup plus a risk score. Because no tool list is published, confirm its capabilities before depending on it.
- Requirements
- A remote streamable HTTP endpoint at the provider's Apify actor URL. Authentication is required: a bearer token supplied in the Authorization header, described as an Apify API token. No packages, environment variables or other credentials are declared. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open Compliance Auditor MCP in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- 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.firasmosbehi%2Fcompliance-auditor/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"compliance-auditor": {
"type": "http",
"url": "https://frayess-mosbehi--compliance-auditor-mcp.apify.actor/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
60% 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.
- License10 pts
Declare a license in the repository or the registry entry.