Britive MCP Serverofficial
F
licenseNot graded
qualityC
maintenanceEnables AI agents and users to interact with the Britive platform for dynamic access, query configurations, reporting, and access activity.
1
-
fes-mcp
by hnegi01
Related Servers
Alternatives to fes-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose an Octopus instance and, when write access is enabled, create releases, deploy releases, run runbooks, and adjust feature toggles.237 npmMIT
- AlicenseAqualityAmaintenanceEnables AI clients to check status, read non-secret settings, schedules, and subject rules, and—when explicitly allowed—update settings and existing subject rules. It also supports local diagnostic workflows while excluding passwords, credentials, arbitrary SQL, files, and shell commands.61MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to retrieve and manage support tickets, comments, and attachments, and to search help center articles as a knowledge base, with each request carrying the operator's own OAuth-authenticated permissions.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Dynamics 365 Business Central environments through natural language commands, including environment, app, session, and extension management.20 npm11MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with OSDU platform services including search, data management, and schema operations.8Apache 2.0
TDQS
A3.6/5.0
Scored across 36 tools
Disambiguation3/5
The domain prefixes and resource nouns separate most tools, but several pairs overlap in obvious ways: get_all_dashboards vs get_dashboards, get_all_datamodel vs get_elasticubes, and get_connection vs get_connections_all require close reading of descriptions to disambiguate. The shared read-only 'get everything' pattern across access, dashboards, and datamodels adds selection risk, so the boundaries are not crisp enough for a higher score.
Naming Consistency4/5
The dominant pattern is domain_prefix_get_resource, and snake_case is used throughout, which makes the set feel predictable. Deviations like access_management_users_per_group, dashboard_can_be_owned, datamodel_describe_datamodel, datamodel_generate_connections_payload, and wellcheck_run_full_wellcheck break the pattern, and singular/plural forms like get_connection vs get_connections_all are inconsistent.
Tool Count2/5
With 36 tools, this server is well above the 25-tool threshold for a heavy surface. The broad read-only scope would feel more manageable if consolidated into fewer aggregate tools per domain, but as-is the agent will carry a large tool list for what is largely a retrieval/wellcheck server.
Completeness2/5
The tool surface is almost entirely read-only: nearly every tool is a getter plus a single wellcheck runner. There are no create, update, delete, or ownership-changing operations, and datamodel_generate_connections_payload mentions create_connections without actually exposing that tool, creating a clear dead end. Agents can inspect the Sisense instance but cannot act on it.
Maintenance
ActivitySlowing
ResponsivenessNo issues