exec-brief
com.basenullPublished by basenull.comOfficial publisherv1.0.0Updated Oct 24, 2026
Weekly 5-15 reports for executive teams: submit reports, fetch the Friday briefing.
The publisher's own server: agent-check
Overview
Lets an assistant submit weekly 5-15 reports for executive teams and fetch the Friday briefing from a hosted service.
- What you can do
- This remote MCP server covers weekly 5-15 reports for executive teams. According to the registry description, it lets an assistant submit reports and fetch the Friday briefing. No individual tools are listed in the manifest, so the exact operations are not documented beyond those two actions.
- When to use it
- Worth adding when a team already runs its weekly 5-15 reporting through exec-brief.basenull.com and wants an assistant to file reports or pull the Friday briefing without leaving the chat. Less useful if you do not use that service or need a documented tool list before adopting it.
- Requirements
- A remote streamable HTTP endpoint at no local runtime or package is needed. A bearer token obtained from the exec-brief.basenull.com dashboard must be supplied in the Authorization header as: Bearer . Network access to that host is required.
Installation
In SourceWeft
- Open exec-brief 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/com.basenull%2Fexec-brief/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": {
"exec-brief": {
"type": "http",
"url": "https://exec-brief.basenull.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 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.
Other Basenull integrations
agent-check
com.basenullOfficial publisher
A remote MCP endpoint for monitoring AI agent runs: it lets an assistant start a run, submit evidence for each task, and complete the run.
polls
com.basenullOfficial publisher
A remote MCP server for one-link team polls, letting an assistant create polls, cast votes, fetch results and close polls.
okr
com.basenullOfficial publisher
Remote MCP endpoint for team OKRs, letting an assistant work with objectives, key results and weekly check-ins from an AI workspace.
agent-talk
com.basenullOfficial publisher
Lets an assistant exchange messages with another AI workspace over a shared channel, wait for replies, and read message history.