Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
MCP server security depends on four controls working together: expose only the tools and permissions a workflow needs, validate every access token for the correct MCP audience, rotate credentials according to their type, and retain structured audit logs only as long as investigation and compliance needs justify. The MCP authorization specification (revision 2026-07-28) does not set one universal log-retention period, so each deployment must document its own schedule.
This guide turns the protocol requirements and current security guidance into settings and operating procedures for local and remote MCP servers.
As an Amazon Associate I earn from qualifying purchases.
What security settings should an MCP server have?
Start with deny-by-default authorization. An MCP server should publish the smallest tool set required for a job, run with a narrowly scoped operating-system or cloud identity, accept only audience-bound tokens issued for that server, and emit tamper-resistant security events with secrets removed. Add network controls and sandboxing when the server executes local code or handles untrusted input.
These controls are layered rather than interchangeable. A perfectly scoped OAuth token cannot compensate for a process that can read an entire home directory. A sandbox does not make it safe to forward a caller’s token to another API. Logging cannot repair an authorization decision that was never enforced. Configure and review each layer independently.
Popular on Amazon
- 【90 Degree Full Function USB C Adapter】Supports the latest USB4 standard for up to 40Gbps of bandwidth, 8K video support, and up to 240W Fast charging; Support USB PD 3.1 Extended Power Range (EPR) including 140W, 180W and 240W. Your productivity is easily doubled. *Warm Tip: For the best fit, please make sure the USB-C port is fully exposed; thick or bulky cases may affect compatibility.
- 【Reliable Quality】Made from high-quality, scratch-resistant aluminum alloy, delicate metal frame. get excellent wear resistance and heat dissipation. Non-Slip Design for easier insertion and removal.
- 【Small and portable】Ultra thin size, ultra compact design, a petite physique that matches the minimalist design of your modern laptops. Coming with a slim figure that won't block the port next to the one it's plugged into.
- 【Compatibility】Widely work with most usb c, thunderbolt 4/3 devices. Compatibilit for ROG Ally, Steam Deck, Switch, MacBook Pro, Quest 3 VR headset, Surface Book 2, iPhone 18/17/16/15, Samsung Galaxy S23/S22/S21, Note 20/10, Google Pixel, ChromeBook, etc.
- 【Excellence Customer Support】If you experience any issues or cable failure, simply reach out to our dedicated customer service team. We provide a prompt response within 18 hours, providing you with the necessary technical support to resolve any concerns.
How does least privilege apply to MCP?
Least privilege means granting each actor, process, tool, and downstream service only the capabilities needed for the current workflow. The MCP authorization specification tells clients to request only necessary scopes, while the MCP security guidance and NSA design considerations extend that principle to tools, hosts, networks, and delegated identities.
1. Limit the exposed tools
Begin with an inventory of the workflow’s required operations. If a client needs to read calendar availability, do not expose write, delete, administrative, or unrelated file-management tools. Separate read and write operations so a scope or policy can allow one without automatically allowing the other. Disable experimental or diagnostic tools in production unless a documented task requires them.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallReview tool descriptions as part of the attack surface. A description that accepts an arbitrary URL, shell command, path, or query deserves stricter validation and policy than a fixed, read-only lookup. Validate arguments against an allowlist of formats, resources, and size limits before the tool executes.
2. Constrain the server process
For a local server, use a dedicated operating-system account with no interactive administrator rights. Grant read access only to specific directories and write access only to required working locations. Block access to credential files, source-control metadata, operating-system configuration, and unrelated users’ data. Run the process in a sandbox, container, or equivalent isolation boundary when practical; treat that boundary as defense in depth, not as a replacement for authorization.
For a remote deployment, restrict outbound network destinations and inbound routes. A server that only needs one data service should not have unrestricted internet egress. Place administrative endpoints on a separate network path, require stronger authentication for them, and keep them out of the tool interface exposed to ordinary clients.
3. Scope downstream identities
The server’s workload identity should have only the permissions needed to perform its own operations. Do not let the server’s broad service role silently become a privilege-escalation path for every caller. Preserve the caller’s identity and authorization context, then apply per-caller policy before using a downstream role.
Where a downstream service supports delegated identity, prefer it over one shared superuser credential. If delegation is unavailable, divide functions across separate service accounts and make each account’s allowed resources explicit. Record which identity performed the downstream action so an investigator can distinguish a user request from an automated maintenance task.
Also popular on Amazon
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
4. Use incremental authorization
Request a narrow baseline scope at connection time and ask for additional authorization only when a specific operation needs it. The protocol describes a WWW-Authenticate scope challenge for the current operation. Scope names in examples are not universal required names; use the authorization server’s documented vocabulary and keep each scope’s meaning precise.
Step-up authorization should be visible to the user or controlling agent. A request to export records, change permissions, or send an external message should not inherit approval merely because a less sensitive read operation was previously approved.
How should an MCP server validate OAuth tokens?
Validate every protected request before invoking a tool or contacting a downstream API. Check the token according to the deployment’s OAuth profile, including signature or introspection status, issuer, expiry, intended audience, required scopes, and any sender-constraint requirement. Fail closed with an authorization error when a token is invalid, expired, intended for another resource, or insufficiently scoped.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →The authorization specification is explicit: MCP servers must not accept or transit any other tokens. An access token issued for one API is not a general credential that can be replayed at an MCP server or passed onward to an unrelated service.
Audience and resource validation
Configure the authorization server so tokens identify the MCP server as their resource or audience. At request time, compare that claim with the server’s configured identifier; do not merely check that the token is signed by a trusted issuer. A valid token for a different resource must be rejected.
After accepting the MCP token, use a separately obtained credential for a downstream API. Token exchange, delegated credentials, or a narrowly scoped workload credential can provide that separation. Never copy the inbound Authorization header into an upstream request as a convenience.
Scope and claim checks
Map each tool to the minimum scope or policy action it requires. A token with a general connection scope should not automatically authorize deletion, administration, or access to another tenant. Check tenant, subject, client, and authentication-strength claims when the deployment’s policy depends on them.
Recommended Free Tools
Also popular on Amazon
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Return a clear protocol-appropriate authorization response without revealing whether a protected resource exists. Keep detailed reasons in an internal security event, with sensitive claims minimized.
Local-server considerations
Local transport does not remove the need for authorization. A malicious local process, compromised desktop account, or untrusted client can still invoke a listening server. Bind to the narrowest interface needed, authenticate local clients where feasible, and use filesystem or operating-system permissions to protect the transport endpoint and configuration.
What is the correct way to rotate MCP credentials?
Rotation depends on credential type; there is no single interval that fits every MCP deployment. Prefer short-lived access tokens, protect refresh tokens, and place unavoidable static secrets under a documented rotation schedule with an overlap period for safe rollout.
| Credential | Recommended handling | Failure and recovery concern |
|---|---|---|
| Access token | Use the shortest lifetime the workflow supports; validate expiry, audience, issuer, and scopes on every request. | Expired or invalid tokens must fail closed. Obtain a new token through the authorization flow rather than retrying indefinitely. |
| Refresh token | Protect in transit and at rest; do not assume one will be issued. For public clients, use sender-constraining or rotation as required by RFC 9700. | Revoke and replace a token when reuse or compromise is suspected. Avoid writing it to logs, crash reports, or shell history. |
| Static API key or secret | Keep it out of source code and plaintext configuration; use a secrets manager when available and rotate on a written schedule. | Support two active versions briefly, if the provider allows, so consumers can switch before the old secret is revoked. |
Design a rotation runbook
- Inventory. Record every token, key, certificate, owner, audience, storage location, creation date, expiry, and dependent service.
- Set policy by type. Define access-token lifetimes, refresh-token reuse detection, and static-secret review and rotation dates. Base the schedule on exposure, provider limits, incident-response needs, and contractual obligations rather than an invented universal number.
- Automate issuance and storage. Retrieve secrets at runtime from a protected store where possible. Restrict who and what can read them, and prevent them from appearing in process listings or debug output.
- Roll forward safely. Create the replacement, deploy it to consumers, verify successful authorization, then revoke the old credential. Keep the overlap as short as operationally safe.
- Exercise emergency revocation. Document who can revoke a credential, how clients obtain a replacement, and how to identify requests made with the compromised value.
For public clients, RFC 9700’s sender-constrained or rotated refresh-token requirement is a security property, not a suggestion to store a long-lived bearer token in a desktop configuration file. If the authorization server cannot provide a secure refresh mechanism, design for interactive reauthorization or another supported flow.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesWhat should MCP security logs contain?
Logs should let an authorized responder reconstruct who or what called which server and tool, which policy decision applied, and what happened next. The NSA’s MCP security design considerations emphasizes that robust observability is essential for MCP environments.
A useful security event normally includes:
- UTC timestamp from a synchronized clock;
- user, agent, service, or workload identity, using a stable non-secret identifier;
- client and server identifiers and versions;
- tool name and operation category;
- request, session, and correlation identifiers;
- authorization result, policy rule, approval or step-up state, and reason code;
- resource or tenant identifier in a minimized, non-sensitive form;
- execution outcome, latency category, and error class; and
- the destination identity for any downstream call.
Centralize events for authorized monitoring and investigation, protect their integrity, and restrict log-reader permissions. Alert on repeated audience failures, scope violations, unexpected tool combinations, refresh-token reuse, unusual export volume, and repeated policy denials. Keep alert payloads as carefully redacted as the underlying event.
What must never be written to ordinary logs?
Do not record raw access tokens, refresh tokens, API keys, private keys, passwords, session cookies, or authorization headers. Avoid full tool arguments and outputs when they contain personal data, confidential documents, health or financial information, prompts, or customer content. The OWASP Logging Cheat Sheet recommends minimizing and protecting sensitive data; apply the same discipline to MCP event streams.
Also popular on Amazon
- Portable and powerful USB-C HUB: BENFEI USB Type-C HUB, with super-soft and knot-free silicone woven design cable, meets most mobile office needs. Compact, lightweight, stylish, and powerful portable USB C Hub equipped with 1 x HDMI port, 1 x 100W charging, and 3 x USB ports. 18-month warranty, 24-hour response, to ensure you feel at ease when using our product.
- Design centered on comfort and reliability: Thanks to BENFEI's end-to-end in-house cable production capability, in-house PCBA and assembly capability, using the industry's most advanced silicone woven design and process, 20cm cable in length, no knots, super-soft, the HUB is easy to use in all scenarios: laptop, tablet, stand etc. Super-soft, 25000+ life cycles, to meet your daily carrying and office needs.
- 100W Charging: Support up to 90W USB C pass-through charging via Type-C port to keep your laptop powered. 10W is reserved for other interface operations. No data and video function on the Type-C port.
- 4K HDMI Display: The HDMI port supports media display at resolutions up to 4K 30Hz, keeping every incredible moment detailed and ultra vivid. Please note that the C port of the Host device needs to support video output.
- Transfer Files in Seconds: Transfer files and from your laptop at speeds up to 10 Gbps with USB A 3.2 port. Extra 2 USB A 2.0 ports are perfectly for your keyboards and mouse.
Use structured redaction before serialization, not a cleanup job after secrets have already reached a log sink. Replace a secret with a fixed marker or one-way fingerprint when correlation is genuinely needed. For arguments, log a schema-approved summary such as record type, count, and classification instead of the raw payload. Test redaction with representative error paths, because exception traces and validation failures often bypass the normal formatter.
How long should MCP logs be retained?
There is no universal MCP retention duration in the reviewed specification or official guidance. Set a documented period from the longest credible investigation window and applicable privacy, legal, regulatory, and contractual requirements, then delete or irreversibly anonymize records when that period ends.
The OWASP MCP Security Testing Guide gives “90 or more days for high-risk MCP systems” as an illustrative example. It is not a protocol mandate, benchmark, or automatic answer for every deployment. A low-risk internal tool may require less; a system subject to long investigations or sector rules may require more, subject to data-minimization limits.
A retention decision framework
- Define the investigation window. Ask how far back responders must correlate an incident, credential compromise, or abuse report.
- Map obligations. Identify jurisdictional privacy rules, sector regulations, discovery requirements, and customer contracts that set minimums or deletion duties.
- Classify event data. Separate low-sensitivity authorization metadata from logs containing resource identifiers or content, and assign shorter periods to more sensitive material where possible.
- Choose storage tiers. Keep searchable, high-value events in a restricted store for active response; move older records to an equally protected archive only when there is a documented reason.
- Document deletion. Record the owner, schedule, legal hold process, deletion method, and evidence that expired records were removed from primary and backup systems.
Retention is not only a storage setting. Limit who can search events, encrypt them in transit and at rest, monitor administrator access, and ensure a legal hold can pause deletion without silently extending every record’s lifetime.
How do local and remote MCP deployments differ?
Local deployments concentrate risk on the workstation: filesystem reach, process isolation, local sockets, and the desktop user’s credentials are most important. Remote deployments add network exposure, multi-tenant authorization, gateway policy, rate limits, and centralized monitoring. Both still require audience validation, least-privilege tools, and redacted events.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Control area | Local emphasis | Remote emphasis |
|---|---|---|
| Execution | Dedicated account, sandbox, restricted paths and egress | Isolated workload, hardened host, controlled ingress and egress |
| Identity | Authenticate local clients and protect desktop-held tokens | Validate issuer, audience, tenant, client, and delegated user identity |
| Downstream access | Prevent reading local credential files | Use narrowly scoped workload or delegated roles; separate tenants |
| Observability | Protect local logs from other users and applications | Centralize events, enforce access controls, alert and correlate across services |
An API gateway can provide a useful enforcement point for remote deployments, including token validation, rate limiting, and audit policy. It does not replace authorization inside the MCP server: the server must still validate the request and prevent unrelated tokens from being accepted or forwarded.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How can you verify that the settings fail safely?
Use a repeatable security checklist in staging and after material configuration changes. The goal is to demonstrate policy behavior, not to assume that a configuration file expresses it correctly.
Also popular on Amazon
- 【Read before You Buy】 Note: This adapter is USB 2.0 version and cannot transmit HDM, VGA, or other video signals. Nevertheless, they are fully capable of charging devices,duplicating files, and can be seamlessly integrated with USB-C earphones, wireless network adapters, and SD card adapters.
- 【Easy to Use and Safe】Thanks to modern manufacturing techniques, we've made these adapters sufficiently compact so that they can remain inserted in your device without noticeable protrusion or inconvenience. This means you don't have to constantly plug and unplug them, reducing the likelihood of wear and misalignment, and making them more convenient to carry around.
- 【Reliable Quality】Engineered for enhanced durability, durable aluminum alloy shell material,get excellent wear resistance and heat dissipation,the male USB C and female USB connectors & the male USB and female USB C connectors are designed to be plugged and unplugged up to 20000 times. Provides data transfer, device charging, memory space expansion, and additional computer peripherals.
- 【Think more for you】Do you need to connect a USB-C-enabled device to an odd device that only has USB-A ports? Then these USB-A male to USB-C female adapters are made for you.Simply insert the adapter into the USB-A port on the device, and you can instantly connect your USB-C device to the device that originally didn't have the correct connection port.
- 【Trusted xiwxi Quality and Service】As a responsible brand seller, you will receive xiwxi's 12-month Quality assurance and lifetime friendly customer service, you're not just buying a product,you're investing in peace of mind with all-round quality and exceptional customer service.
- Call a tool that is not exposed to the client; confirm it is unavailable.
- Use a correctly signed token with the wrong audience; confirm the request is rejected before tool execution.
- Use an expired token and a token missing the required scope; confirm both fail closed with safe errors.
- Attempt a path, URL, tenant, or operation outside the allowlist; confirm validation blocks it.
- Inspect downstream requests; confirm the inbound MCP token is not forwarded.
- Trigger validation, exception, and timeout paths; verify that tokens, keys, and sensitive arguments remain redacted.
- Search centralized logs using a correlation ID and confirm an authorized responder can reconstruct the decision and outcome.
- Revoke and rotate a credential; verify old values stop working and the replacement is accepted.
- Run the retention job in a non-production copy; verify expired records and derived indexes are removed while legal holds are respected.
Which settings should be reviewed periodically?
Review tool exposure and scopes whenever a workflow changes, not only during an annual audit. Reconcile the server’s declared tools with the code actually deployed, compare downstream roles with observed operations, and remove unused permissions. Review token issuers, audience identifiers, redirect and refresh-token settings, secret owners, and rotation dates after every identity-system change.
For logs, sample events for completeness and redaction, inspect who has queried them, verify clock synchronization and integrity controls, and recalculate retention when an investigation window, contract, or law changes. Keep a versioned record of the decision and its owner so operators can explain why a setting exists.
How we derived the settings
The recommendations combine requirements and guidance from the MCP authorization specification, MCP security best practices, the NSA’s 2026 design considerations, OWASP’s MCP and logging guidance, Microsoft Learn’s remote-deployment guidance, and RFC 9700. The protocol requirements are distinguished from deployment choices: MCP requires rejecting unrelated tokens, while retention duration, static-secret cadence, and exact scope names remain policy decisions that must fit the environment.
Frequently Asked Questions
Can an MCP server use one long-lived API key for every user?
That design removes per-user accountability and makes compromise harder to contain. Prefer delegated or per-workload credentials with narrow permissions; if a static key is unavoidable, isolate its role, store it in a protected secret store, monitor its use, and rotate it on a documented schedule.
Should refresh tokens be stored on the MCP server or on the client?
Store a refresh token only in the component that owns the authorization flow, using protected storage and encrypted transport. Do not copy it into server logs, tool arguments, or downstream requests, and do not assume that every authorization flow issues one.
What is a safe way to correlate MCP logs without logging personal data?
Use stable opaque identifiers for the subject, request, session, tenant, and resource, and keep the mapping in a separately protected system when it is needed. Log categories, counts, and policy outcomes instead of full content, and apply the same minimization to traces and error reports.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →What happens if a downstream API needs a different audience than the MCP server?
The server should obtain a separate downstream credential through token exchange, delegation, or a narrowly scoped workload identity. It must not forward the inbound MCP bearer token, even when both services trust the same issuer.

